RBM_CLI(7)

πŸ“¦
version 0.4^20241205gitc6a4095 Β· 2 versions
, in fedora 43

πŸ’– 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 πŸ‘‘ see rbm_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 the showconf command. when you're using the build command, 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-args and --gpg-bin all 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