ELN Content Set

RHEL maintainers should add a package to ELN when it intended to be added to the next major version of RHEL. (Often, it is also being added to the current stable version of RHEL at the same time.)

You add binary packages by creating and submitting workloads for Content Resolver. You submit them as pull requests at Content Resolver input. The workloads go in the config directory.

Once the workloads have been merged, Content Resolver works through all the dependencies of the workload, and displays it in its ELN view.

After Content Resolver has worked it work, the ELN build automation takes that list and adds it to the ELN build list, and drops any packages which are no longer on that list.

The next step is to add the binary packages to the appropriate repositories, so that they "ship" in the ELN compose. Most explicitly added packages will end up in one of the two following repositories:

The content of those repositories are defined in pungi-fedora.

If the package has a -devel subpackage, or brings in build dependencies which are not needed at runtime, that would be useful for building other packages (such as in EPEL), then they should be added to the following repository:

The content of CRB is defined in ELN’s crb group of fedora-comps.

The following RHEL Add-Ons have corresponding repositories in ELN for their specific content:

The content of those repositories is defined in their respective groups of fedora-comps.

While technically not part of the RHEL compose or package set, an equivalent to RHEL Extensions is also available:

The content of this repository is defined in pungi-fedora.