almalinux
/
lorax
14
0
Fork 0
Code Issues Pull Requests Releases Activity

lorax-composer: Clarify groups documentation 

Also remove the note about versions not being used for depsolving, as
well as add an example for packages in the blueprint.
This commit is contained in:
Brian C. Lane 2019-07-31 10:26:42 -07:00
parent 12e632a058
commit 1983bddb65
1 changed files with 26 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/lorax-composer.rst
View File

@ -156,14 +156,26 @@ The names must match the names exactly, and the versions can be an exact match
or a filesystem-like glob of the version using ``*`` wildcards and ``?`` or a filesystem-like glob of the version using ``*`` wildcards and ``?``
character matching. character matching.
NOTE: As of lorax-composer-29.2-1 the versions are not used for depsolving, NOTE: Currently there are no differences between ``packages`` and ``modules``
that is planned for a future release. And currently there are no differences in ``lorax-composer``. Both are treated like an rpm package dependency.
between ``packages`` and ``modules`` in ``lorax-composer``.
For example, to install ``tmux-2.9a`` and ``openssh-server-8.*``, you would add
this to your blueprint::
[[packages]]
name = "tmux"
version = "2.9a"
[[packages]]
name = "openssh-server"
version = "8.*"
[[groups]] [[groups]]
~~~~~~~~~~ ~~~~~~~~~~
These entries describe a group of packages to be installed into the image. Package groups are The ``groups`` entries describe a group of packages to be installed into the image. Package groups are
defined in the repository metadata. Each group has a descriptive name used primarily for display defined in the repository metadata. Each group has a descriptive name used primarily for display
in user interfaces and an ID more commonly used in kickstart files. Here, the ID is the expected in user interfaces and an ID more commonly used in kickstart files. Here, the ID is the expected
way of listing a group. way of listing a group.
@ -172,6 +184,16 @@ Groups have three different ways of categorizing their packages: mandatory, def
For purposes of blueprints, mandatory and default packages will be installed. There is no mechanism For purposes of blueprints, mandatory and default packages will be installed. There is no mechanism
for selecting optional packages. for selecting optional packages.
For example, if you want to install the ``anaconda-tools`` group you would add this to your
blueprint::
[[groups]]
name="anaconda-tools"
``groups`` is a TOML list, so each group needs to be listed separately, like ``packages`` but with
no version number.
Customizations Customizations
~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~