1RBM_MODULES(7)                                                  RBM_MODULES(7)
2
3
4

NAME

6       rbm_modules - rbm modules
7

DESCRIPTION

9       An rbm workspace can contain a number of different projects. In some
10       cases it can be useful to share some of those projects between multiple
11       workspaces. This can be done using modules.
12
13       A module is a subdirectory in the modules directory. If you are using
14       git, it is possible to store each module directory using a separate
15       git-submodule.
16
17       A module directory structure is similar to the main workspace
18       structure: each module includes a projects directory containing the
19       projects, a keyring directory containing the gpg keyrings used by the
20       projects, and a rbm.module.conf containing rbm configuration related to
21       the projects included in the module.
22

RBM CONFIGURATION

24       The rbm configuration from a module (the rbm.module.conf and the
25       project config files) can define any configuration option. However, for
26       clarity and to avoid name collisions with other modules or with core
27       rbm options, it is recommended to prefix all option names
28
29       The workspace configuration (rbm.conf) has priority over the modules
30       configuration (rbm.module.conf). Module configuration is used in
31       alphabetical order: configuration from a module named A will have
32       priority over a module named B. See rbm_config(1) for more details.
33

KEYRING

35       The keyring directory in a module contains gpg keyring files (see the
36       gpg_keyring option). If a keyring file is available in multiple
37       modules, the one from the first module in alphabetical order will be
38       used. If a keyring file is also available in the main workspace’s
39       keyring directory, then it will be used.
40

SEE ALSO

42       rbm(1), rbm_config(1)
43
44
45
46                                  01/20/2023                    RBM_MODULES(7)
Impressum