EPEL 10 bikeshedding: pointing users at the right repo

I’ve been thinking through the dnf variable approach, and I think that will work best with a slight tweak of the proposed repo path. As implemented in the proof of concept, the file trigger will set epelrelease to 10.0 on RHEL 10.0, and simply 10 on CentOS Stream 10. To avoid requiring code changes for MirrorManager (see EPEL 10 proposal - #17 by adrian) to redirect 10 to the latest minor version, we can just have the epel10 dist-git branch populate an epel/10 repo path (instead of the originally planned epel/10.x path).

branch built against dist tag repo
epel10 CentOS Stream 10 .el10_1 epel/10.1 10
epel10.0 RHEL 10.0 .el10_0 epel/10.0
1 Like