Packages for Rootbeer, with package recipes for Apple silicon macOS and Linux on ARM64 and x86-64. Availability varies by package.
Browse packages · Install Rootbeer · Package guide
Run a tool without creating a Rootbeer configuration:
rb run jq -- --versionKeep it available for everyday use:
rb use jq
eval "$(rb env)"
jq --versionAdd @version to pin an exact release, such as jq@1.8.2, and run
rb use --update to move to what the index has now. You can also manage packages
alongside your dotfiles with rb.package("jq") in your Lua configuration.
Packages can also export macOS apps. rb use bobrwm links Bobrwm.app into
~/Applications, and existing apps are never overwritten.
Packages install into the shared store at /opt/rb, only by the digests the signed
index lists. Clients from before /opt/rb
read the frozen https://pdr.rbpkg.com/v3/current.json, whose last rootbeer moves
them onto /opt/rb. Run rb migrate once to move what they installed.
Recipes live in packages/, one Lua file per tool. Start with an
existing recipe such as jq.lua.
- Use the canonical lowercase name and exact upstream versions.
- Each version lists its source or asset digest per platform under
digests. - Add a version with
rb drv bump <name> <version> --keep 2. The index keeps every version it signed, so a recipe keeps only what CI should still build. Shared fields apply to every retained version, so give a build change to one version as an override on that version. - Dependencies name no version, so they follow the dependency's default and an
update to it rebuilds what uses it, such as a go or openssl fix. Pin a
versiononly when a recipe needs that exact one. - Keep patches as
.patchfiles in a directory named after the recipe, such aspackages/krb5/, and list their file names in order undersource.patches. - Declare only platforms you can verify, with checks that exercise the tool.
Build and check a package locally, with an rb from rootbeer at
.github/rb-engine-revision or newer:
rb drv build jqPackages plans every declared version against
ghcr.io/rootbeer-org/store and builds only what the store lacks, one job per
platform in dependency order. A failed package holds back only what depends on it.
PRs build and check the keys they change and stage each output in
ghcr.io/rootbeer-org/staging once it passes. Main installs what staging has
instead of rebuilding it, publishes to the store, and runs every six hours to
build whatever is still missing. Then the
index repository signs the new entries
with a key this repository never sees. Rerun runs
a failed run's jobs again when no package failed, so a lost runner or a registry
error resumes from what was staged. Prune staging
deletes staged outputs after 14 days.
Rootbeer packages each commit rootbeer's CI publishes. It adds the version as the default, moves the engine pin, keeps the newest three versions, and merges once its checks pass. The index keeps every version it signed, so trimming loses nothing.
Updates runs rb drv updates daily and opens a PR
per package with a newer stable upstream version, written by rb drv bump and
keeping two versions. Those PRs wait for review. Recipes without an upstream, and
Sparkle ones, are updated by hand.
For a missing tool, broken package, or outdated version, open an issue here.
Include the package, requested version, platform, and error output when applicable.
For problems with rb itself, use the Rootbeer repository.