2ea74164a5
With the advent of alternative bootloaders (systemd-boot) whether or not grubby gets installed should be dependent on whether grub is selected as the bootloader. This currently happens correctly with anaconda and the grub dependencies, so it can be removed safely. That allows systemd-boot to be installed cleanly without grubby drippings confusing it. Sync F40 with F39 since the branch happened before the commit was merged. Signed-off-by: Jeremy Linton <jeremy.linton@arm.com> |
||
---|---|---|
ci | ||
po | ||
.gitignore | ||
.zuul.yaml | ||
check-missing | ||
comps-cleanup.xsl | ||
comps-el4.xml.in | ||
comps-el5.xml.in | ||
comps-el6.xml.in | ||
comps-eln.xml.in.in | ||
comps-epel7.xml.in | ||
comps-epel8-next.xml.in | ||
comps-epel8.xml.in | ||
comps-epel9-next.xml.in | ||
comps-epel9.xml.in | ||
comps-f7.xml.in | ||
comps-f8.xml.in | ||
comps-f9.xml.in | ||
comps-f10.xml.in | ||
comps-f11.xml.in | ||
comps-f12.xml.in | ||
comps-f13.xml.in | ||
comps-f14.xml.in | ||
comps-f15.xml.in | ||
comps-f16.xml.in | ||
comps-f17.xml.in | ||
comps-f18.xml.in | ||
comps-f19.xml.in | ||
comps-f20.xml.in | ||
comps-f21.xml.in | ||
comps-f22.xml.in | ||
comps-f23.xml.in | ||
comps-f24.xml.in | ||
comps-f25.xml.in | ||
comps-f26.xml.in | ||
comps-f27.xml.in | ||
comps-f28.xml.in | ||
comps-f29.xml.in | ||
comps-f30.xml.in | ||
comps-f31.xml.in | ||
comps-f32.xml.in | ||
comps-f33.xml.in | ||
comps-f34.xml.in | ||
comps-f35.xml.in | ||
comps-f36.xml.in | ||
comps-f37.xml.in | ||
comps-f38.xml.in | ||
comps-f39.xml.in | ||
comps-f40.xml.in | ||
comps.dtd | ||
comps.rng | ||
Makefile | ||
README.md | ||
update-comps | ||
update-eln-extras-comps |
Fedora Comps
comps files are XML files used by various Fedora tools to perform grouping of packages into functional groups.
How comps is used
Installation
comps is used by the installer during package selection. On the Software Selection screen, environment groups (as defined by the environment
keyword in comps.xml
) are listed down the left-hand side. All optional groups (defined by the group
keyword) for that environment (listed in the environment's optionlist
) are shown at the top of the right-hand pane. Other groups which have uservisible
set are displayed lower in the right-hand pane.
At install time, the installer will usually install the mandatory
, default
and appropriate conditional
packages from all groups listed in the selected environment group's grouplist
, plus those from any optional groups the user selected on the right-hand side. See below for more details on these 'levels'.
Running System
In dnf, groups and environment groups are used by the dnf group install
and dnf group remove
commands, and can be queried with the dnf group list
command. There are many others besides these: see the dnf documentation for more on this.
Tree, Release, and Image Composition
The kickstart files in fedora-kickstarts use the group and environment group definitions from comps. Multiple tools use these kickstarts to compose different types of images, and the release trees. The manifests for rpm-ostree-based Fedora variants in workstation-ostree-config (the name is a misnomer these days) are synced against comps using the comps-sync.py
script, and used to define the package sets included in those variants.
Package levels
In any group, there are four levels of packages: optional
, default
, mandatory
, and conditional
.
mandatory
- these packages must be installed for the group to be considered installeddefault
- these packages are installed by default, but can be removed while the group is still considered installedoptional
- these packages are not installed by default, but can be pulled in by kickstart or dnf optionsconditional
- these packages are brought in if theirrequires
package is installed
When using the interactive installer, you cannot include optional
packages. However, if using a kickstart, you can add the --optional
option for a group to specify that its optional packages should be included. Similarly, when installing a group with dnf
, you can pass --with-optional
to include the optional packages.
Categories
Categories are barely used any more. They used to be something like environment groups for an older form of the Fedora installer. Some older graphical package management tools can still display these categories.
Developing comps
For Fedora packagers:
git clone ssh://git@pagure.io/fedora-comps.git
For others:
git clone https://pagure.io/fedora-comps.git
When changing the packages, make sure the file is sorted. This helps to make it more maintainable. Use make sort
command to fix the sorting. Also run make validate
to check for XML syntax errors. You can submit pull requests using the common Github-style workflow - fork the repository from the web UI, push your changes to your fork, and submit a pull request for it. If you are not familiar with this workflow, see the Pagure documentation.
For more info
For more information, including rules on how and when to edit comps, see the Fedora project wiki.
Bugs against comps can be filed as Pagure issues.