fedora config files for pungi
Go to file
Josh Boyer 33db513c03 Move dracut-tools to BaseOS
Signed-off-by: Josh Boyer <jwboyer@redhat.com>
2020-12-01 13:12:28 -05:00
fedora Skip s390x until https://pagure.io/releng/issue/9875 is fixed. 2020-12-01 07:39:45 +01:00
shared Move dracut-tools to BaseOS 2020-12-01 13:12:28 -05:00
content-resolver-to-gather-source-json ELN: Try building Base container image. 2020-09-16 09:19:17 +02:00
eln.conf ELN: Use the "global variable" feature to reduce config duplicities. 2020-10-07 07:38:00 +02:00
prepopulate.json ELN: Add prepopulate.json as placeholder and defined gather_method for Buildroot. 2020-10-08 08:16:25 +02:00
README.rst ELN: Try building Base container image. 2020-09-16 09:19:17 +02:00
variants.xml Include emacs group in AppStream. 2020-11-18 09:36:37 +01:00

This repository holds the config files that define Fedora ELN compose, 
Future CentOS Stream compose and Future RHEL compose.

The repository is organized into several directories:

- ``shared`` - Pungi configuration files defining compose options
  which are shared between all Fedora ELN, CentOS Stream and RHEL.
  There is one Pungi configuration file for each Pungi phase and
  also ``general.conf``, ``multilib.conf`` and
  ``additional_and_filter_packages.conf`` defining compose options
  which are not specific for any particular phase.
- ``fedora`` - Pungi configuration files which extend the ``shared``
  compose options (and in some cases overrides them) for Fedora ELN
  compose.
- ``centos`` - Pungi configuration files which extend the ``shared``
  compose options (and in some cases overrides them) for CentOS
  compose.
- ``rhel`` - Pungi configuration files which extend the ``shared``
  compose options (and in some cases overrides them) for RHEL
  compose.

In the main directory, there is one file for each compose which can
be generated from thie configuration files repository. Each config
file imports the ``shared`` configuration files and also the ``fedora``,
``centos`` or ``rhel`` specific overrides.

Compose variants (repositories)
###############################

So far the compose repositories are defined by the Content Resolver.
There is a ``content-resolver-to-gather-source-json`` Python script
which queries the Content Resolver API and generated ``gather_source.json``
which defines which RPM is in which Compose variant.

In the future this will be replaced by comps files, but these are not
defined yet.