For the complete documentation index, see llms.txt. This page is also available as Markdown.

Contribution

Contribution guidelines

  1. Read the packaging section, especially the recipe reference and the examples

  2. Look at existing packages for something close to what you are adding

  3. Scaffold the recipe, pin a version, and check it:

sbuild new mypkg owner/repo --type static
$EDITOR packages/mypkg/pkg.toml

sbuild resolve . mypkg
sbuild hashfill
sbuild validate
sbuild audit . mypkg --host x86_64-linux
  1. Open a pull request, or an issue if you would rather someone else write it

sbuild validate is the gate in CI, so a branch that passes it locally will not fail there for a reason you could have seen. Commit both pkg.toml and the version file. A pinned URL without a hash beside it is the one state validation refuses.

We will help fix any mistakes and give feedback on the pull request. See tooling for what each command does and where to get sbuild.

Last updated