Go to file
Stephen Gallagher 89bf5aa3c3
Add libselinux-python to the ansible-node group
If the target system has SELinux present, we need to make sure
that we have libselinux-python available or else nearly all Ansible
modules will fail with the error "Aborting, target uses selinux but
python bindings (libselinux-python) aren't installed!"

Resolves: RHBZ#1374491

Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
2016-09-08 16:11:43 -04:00
.tx
po update po/POTFILES.in for f26 2016-07-26 17:45:13 +01:00
.gitignore
comps-cleanup.xsl Add some env bits to comps-cleanup.xsl 2013-04-23 15:56:26 -04:00
comps-el4.xml.in
comps-el5.xml.in Fix typo: epel-rpm-config -> epel-rpm-macros. 2016-04-01 19:34:43 -05:00
comps-el6.xml.in add epel-rpm-macros to el6 comps 2016-01-20 14:20:35 -06:00
comps-epel7.xml.in Merge #30 fix util-linux package name in epel7 2016-07-01 00:01:24 +00:00
comps-f7.xml.in
comps-f8.xml.in Fix sort order introduced in r1.285: move lxde packages to windowmanagers 2009-02-15 13:00:04 +00:00
comps-f9.xml.in Revert "Remove eject, merged into util-linux" 2012-09-06 14:09:14 +02:00
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 Remove retired netcat tools (nc and nc6) 2016-06-20 18:58:16 -04:00
comps-f20.xml.in Remove retired netcat tools (nc and nc6) 2016-06-20 18:58:16 -04:00
comps-f21.xml.in Remove retired netcat tools (nc and nc6) 2016-06-20 18:58:16 -04:00
comps-f22.xml.in Sort and indent and clean up all current comps files. 2016-06-23 10:57:08 -06:00
comps-f23.xml.in Update ruby and rubyonrails group 2016-09-06 12:33:11 +02:00
comps-f24.xml.in Add libselinux-python to the ansible-node group 2016-09-08 16:11:43 -04:00
comps-f25.xml.in Add libselinux-python to the ansible-node group 2016-09-08 16:11:43 -04:00
comps-f26.xml.in Add libselinux-python to the ansible-node group 2016-09-08 16:11:43 -04:00
comps.dtd comps.dtd, comps.rng: add environment and optionlist 2014-02-17 10:47:27 +09:00
comps.rng Fix indentation in environment definition 2016-05-18 14:43:57 +02:00
Makefile add f26 comps file and use it for rawhide 2016-07-26 06:44:17 +01:00
README.md Migrate README to Markdown 2016-05-16 19:20:58 +02:00
update-comps Fix permissions on update-comps 2015-09-18 10:39:02 -06:00

Fedora Comps

comps is a XML file 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. At the Default Packages dialog , the user can choose to Customize Now, displaying the Category Selection dialog.

In the category selection dialog , categories (as defined by the category keyword in comps.xml) are listed down the left-hand side. If a category is selected, any groups in that category with uservisible set are displayed in the right-hand pane. Groups have an icon associated with them. These icons come from the comps-extras package; icons are read from /usr/share/pixmaps/comps/<group-id>.png. If an icon does not exist for a group id, the one for the category that the group is in is used.

Once a group is selected, clicking the Optional Packages button shows the Package Selection dialog.

In any group, there are four levels of packages: optional, default, mandatory, and conditional:

  • optional are not automatic but can be checked
  • default are, but can be unchecked in a gui tool
  • mandatory are always brought in (if group is selected), and not visible in the Package Selection dialog.
  • conditional are brought in if their requires package is installed

Usually optional is the way, however if you feel that your package deserves a default or required level bring it up for discussion on the development lists. Remember that this has effect on whether or not your package winds up on distribution media such as Live images and spins.

Running System

In dnf, groups are used by dnf groupinstall and dnf groupremove commands, and can be queried with dnf grouplist command.

In PackageKit (Add / Remove Software) the upper left quadrant shows Package collections. When this is clicked, the grouping information is loaded from the configured software repositories, and the complete list of groups, stripped from their categories, are shown in the right hand pane. Selecting a group for installation causes only the default packages within the group to be installed.

Developing comps

git clone ssh://git@pagure.io/fedora-comps.git

Tree, Release, and Image Composition

The kickstart files in fedora-kickstarts use the group definitions from comps to compose images and release trees.

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 in bugzilla.