RBM_CLI(7)
π rbm_cli β the rbm command line interface π
okay bestie, welcome to rbm_cli(7) β yes that's the manpage name, it's giving very "section 7, miscellaneous" and honestly? iconic. this is where you learn how to actually talk to rbm from your terminal, and no cap, it's easier than it looks π«Ά
β¨ SYNOPSIS β¨
rbm <action> <project> [options]
like. that's the whole shape of it. action first, then the project, then whatever little flags your heart desires πΈ
π¦ DESCRIPTION π¦
so the rbm commands? they usually take an action as the first argument, then a project's name, then some options. that's the vibe. action, project, options, slay, done π
π COMMAND LINE OPTIONS π
okay so here's the tea β β a lot of the configuration options that you can set in the main config file and in the project config files can also be overridden right from the command line. main character energy.
the naming rule is literally so simple it's cute:
- the command line option name is the same as the configuration file option
- but you prepend it with
-- - and every
_gets swapped for a-
so like, output_dir: out in the config file? you can just hit it with --output-dir=out instead. periodt β¨
here's every single option you can set on the command line, no skipping, we're doing all of them π
--sysconf-file=<file>β set the optional system configuration file path--localconf-file=<file>β set the optional local configuration file path--target=<target>β set the target. and bestie, you can use this option multiple times to use more than one target at once π seerbm_targets(7)for the details--output-dir=<directory>β set the output directory--build-log=<filename>β set the file where the build logs get written. if the value is-(which is the default), the logs go out on stdout and stderr--version=<version>β set the package version--pkg-rel=<rel>β set the package release number--distribution=<distribution>β the name of the linux distribution to build the package for--fetch,--no-fetchβ whether the latest commits should be fetched from the remote git repository or not--debug,--no-debugβ enable or disable debug mode: this opens a shell in the temporary build directory if a build failure happens π (very "let me look at what went wrong in there" of it)--stepβ this sets the current step when you're using theshowconfcommand. when you're using thebuildcommand, it's used to select the step (and the build script of the same name) to start from--git-hash=<hash>β the git hash of the commit / tag to use--hg-hash=<hash>β the mercurial hash of the commit / tag to use--commit-gpg-id=<GPG ID>β check that the commit is signed by this GPG key ID π--tag-gpg-id=<GPG ID>β check if the selected git hash is a tag, and that it's signed by the selected GPG key ID--gpg-keyring=<file>β GPG keyring filename--gpg-keyring-dir=<directory>β directory containing GPG keyring files--gpg-args=<args>β optional gpg arguments--gpg-bin=<path>β path to the gpg binary
ngl, the gpg ones are a whole lil cluster β if you're doing signed-commit checking, you're gonna want--commit-gpg-id,--tag-gpg-id,--gpg-keyring,--gpg-keyring-dir,--gpg-argsand--gpg-binall in your mental notes π§
π SEE ALSO π
go read those next, they're the sequel and the prequel respectively, iykyk π
and that's the page!! this one is dated 07/25/2025 and it's page RBM_CLI(7) of the manual β so when you cite it in your notes, that's the receipt π§Ύβ¨ mwah, go build something, bestie πππ¦
π¦ where this page comes from
- fedora 43: rbm 0.4^20241205gitc6a4095-3.fc43 Β· CC0-1.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms