ELN Extras automatically creates EPEL-like builds of packages built on
top of ELN, which allows for early build and dependency testing of
packages which are candidates for the next versions of EPEL. While RHEL
10 has already branched from ELN, it still hasn't diverged all that much
from rawhide, so testing now will also (and in fact already has) help
detect potential issues building EPEL 10. Results of ELN Extras are
displayed in Content Resolver:
https://tiny.distro.builders/view--view-eln-extras.html
Here is an example of a workload-specific CR config:
https://github.com/minimization/content-resolver-input/blob/main/configs/eln_extras_gedit.yaml
And an example of a maintainer catch-all CR config:
https://github.com/minimization/content-resolver-input/blob/main/configs/eln_extras_yselkowitz.yaml
You can add packages to ELN Extras by creating your own configs through
a PR in the following repo:
https://github.com/minimization/content-resolver-input/
--
Yaakov Selkowitz
Principal Software Engineer, Emerging RHEL
Red Hat, Inc.
--
_______________________________________________
epel-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
