RBM_MODULES(7)

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

πŸ’– RBM_MODULES πŸ’–

okay so bestie, welcome to rbm_modules β€” the manual page about, you guessed it, rbm modules ✨ it's section 7, it's giving "deep lore of the rbm universe", and honestly? it's not even that long. we got this. 🫢


🌸 DESCRIPTION 🌸

so here's the vibe: an rbm workspace can hold a whole bunch of different projects, right? and sometimes β€” not always, but sometimes β€” it's genuinely useful to share some of those projects between multiple workspaces. and that, my love, is what modules are for. πŸ’…

A module is literally just a subdirectory in the modules directory. that's it. that's the whole thing.

and if you're using git? oh you're gonna love this β€” it's possible to store each module directory using a separate git-submodule. cute, organized, iconic. πŸ”₯

a module's directory structure is basically a mini-me of the main workspace structure:

  • a projects directory containing the projects πŸ“
  • a keyring directory containing the gpg keyrings used by the projects πŸ”‘
  • a rbm.module.conf containing rbm configuration related to the projects included in the module βš™οΈ

so yeah. same shape, smaller scale. main character energy but in miniature. πŸ‘‘


⭐ RBM CONFIGURATION ⭐

the rbm configuration from a module β€” that's the rbm.module.conf and the project config files β€” can define any configuration option. no gatekeeping. πŸŽ€

however (and this is the part where we're being responsible besties), for clarity and to avoid name collisions with other modules or with core rbm options, it is recommended to prefix all option names.

⚠️ heads up: the original page's sentence genuinely trails off right there after "prefix all option names" β€” no cap, that's how it ends. we're not inventing the rest, we're just reporting the facts. πŸ’€

now, the priority tea β˜•: the workspace configuration (rbm.conf) has priority over the modules configuration (rbm.module.conf).

and when it comes to module configuration, it's used in alphabetical order β€” so configuration from a module named A will have priority over a module named B. alphabet supremacy, fr fr. πŸ”€

want the full picture? go read rbm_config(1) for more details. iykyk. πŸ’œ


πŸ”‘ KEYRING πŸ”‘

the keyring directory in a module contains gpg keyring files β€” peep the gpg_keyring option for the deets. πŸ—οΈ

now the rules of who-wins:

  • if a keyring file is available in multiple modules, the one from the first module in alphabetical order will be used. πŸ₯‡
  • if a keyring file is also available in the main workspace's keyring directory, then it will be used. πŸ‘‘

so basically: main workspace beats modules, and alphabet beats vibes. simple as. ✨


🌈 SEE ALSO 🌈

go read those too, bestie, they're part of the story. πŸ¦‹


and that's the whole page!! mwah πŸ’‹ this was RBM_MODULES(7) from the rbm source, dated 07/25/2025 β€” thanks for reading, ily, go configure something beautiful. πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from