From Fedora Project Wiki

If you maintain an application which makes sense for a user to select during installation, check out the comps module and make sure that your package is listed in a reasonable group in the files (n = number of release; note the files for Fedora Extras ≤ 6 are named If it's not, please add it using the following as a template if your package were named "foo":

<packagereq type="optional">foo</packagereq>

  • Make sure to preserve the alphabetical order in each group.
  • Make sure to run xmllint on the result to check you didn't make a mistake in the XML syntax.

You can use the provided xslt filter to sort, indent and check the syntax of your comps file in one run:

$ xsltproc --novalid -o sorted-file comps-cleanup.xsl original-file

The filter will warn you if it removes redundant information or if something needs to be checked by a human.

If you think there needs to be a new group, please post on fedora-devel-list.

How comps is used


comps is used by the installer during package selection.

Default Packages dialog

At the Default Packages dialog , the user can choose to Customize Now, displaying the Category Selection dialog. In the category selection dialog

Category Selection dialog

, categories (as defined by the category keyword in <file>comps.xml</file>) 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

Package Selection dialog

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 fedora-devel-list. 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 yum, groups are used by yum groupinstall and yum groupremove commands, and can be queried with yum 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.

Package selection

  • If your app will show up in the application menu of the desktop, it should be included
  • Libraries should not be included - they will be pulled in via dependencies
  • Most text-mode utilities don't really fit in unless they have a pretty large established user-base.

If you have questions as to whether it makes sense or not, feel free to post to fedora-devel-list.

Some guidelines on specific groups in comps follows.

New groups

Please consult fedora-devel-list before adding new groups.

New group names and descriptions are translatable strings. Do not add new groups, or change their descriptions, during a string freeze. Please check the release schedule for these dates.


Core is not visible, so adding 'default' or 'optional' packages to it isn't needed. Boot loaders are listed as 'default' in the group so that they're pulled in by compose tools.

Core is installed on every installation, so adding packages to it is discouraged.

GNOME Desktop

The gnome-desktop group is maintained by the Desktop SIG. Please run changes through fedora-desktop-list.

KDE Desktop

The kde-desktop group is maintained by the KDE SIG. Please run changes by them.


The following is part of the Fonts SIG packaging rules.

Fonts for a particular linguistic region used to be bundled in fonts-region packages. Nowadays this practice is frowned upon, fonts package naming reflects upstream naming like in any other Fedora package, and grouping is achieved through comps groups.

  • Font packages in a legacy format (not TTF or OTF) MUST be registered in the legacy-fonts group.
  • Font packages in a non-legacy format (TTF or OTF):
    1. MUST be registered in the fonts group:
      • except when they don't have an active upstream, in which case putting them in legacy-fonts is fine.
    2. SHOULD also be registered in every applicable xxx-support localization group:
      • except groups that only require glyphs in the basic latin range.
      • if a font package adds support for a script previously not supported by Fedora the associated localization groups MUST be created and filed, and the relevant localization teams notified.
    3. SHOULD be declared optional, unless:
      • they add support for a new script, in which case they MUST be declared required in the associated localization groups.
      • they add better support for already supported scripts, in which case, if the localization team in charge of each localization group agrees:
        • they can replace existing fonts as mandatory if this script is not covered by distribution-wide default fonts.
        • they can replace existing fonts as default if this script is covered by distribution-wide default fonts.

Fonts in Fedora
The Fonts SIG takes loving care of Fedora fonts. Please join this special interest group if you are interested in creating, improving, packaging, or just suggesting a font. Any help will be appreciated.

Language support groups

Language support groups are selected automatically if you are installing in the specified language, and manually otherwise. Language support groups require the langonly key, which should be set to ISO 639-1 two-letter language code for that language, or the ISO 639-2 bibliography code, if that does not exist. These codes can be looked up in the iso-codes package.

Each language support group should have the following conditional packages, if the packages exist:

  • hunspell dictionary for the language (requires hunspell)
  • aspell dictionary for the language (requires aspell)
  • langpack (requires
  • KDE 4 translations (kde-l10n-XXX,requires kdelibs)
  • KDE 3 translations (kde-i18n-XXX,requires kdelibs3)
  • KOffice langpack (requires koffice)
  • Eclipse NLS support (requires eclipse-platform)
  • man page translation (requires man-pages)
  • gcompris sounds for the language (requires gcompris)
  • moodle translations (requires moodle)

There may be other language specific subpackages necessary; this is not a fully inclusive list.

Each language support group should have mandatory packages for:

  • fonts required for that locale (consult the Fonts SIG)
  • input methods, and data, required for that locale (consult the I18N SIG)

Each language support group can have optional packages for:

  • additional fonts that support that locale (consult the Fonts SIG)

New language support groups need added to the language-support category in the comps file.

How it works

Checkout the comps CVS module:

cvs -d :ext:<username> co comps

then edit the proper comps-f<x> file and commit your changes.

Please make sure to run cvs update right before cvs commit to avoid overwriting other people's changes as much as possible

Current status

You can check our current comps status file there.