# :computer: EPEL 11 replacing ELN Extras 11 :::info :exclamation: This document is a work-in-progress. Nothing in it has been finalized yet. ::: ## :beginner: Design Goals * Enable the launch of EPEL 11 concurrently with CentOS Stream 11 * Simplify the developer story around EPEL 11 ## :wrench: High-level Design * ELN Extras will be replaced by EPEL 11 in the [Content Resolver](https://https://tiny.distro.builders/view--view-eln-extras.html). * EPEL 11 will be configured to build against the ELN (CentOS Stream 11 preview) buildroot. * The ELNBuildSync tool will be updated to auto-rebuild opted-in EPEL 11 packages from Rawhide. * EPEL 11 will be a "quiet release" prior to the launch of CentOS Stream 11 *** :::warning The following items can make this document more complete. ::: ## :feet: Implementation ### Koji Target The `epel11` target will be available in Koji for building packages against EPEL 11. The builds from this target will be produced using a modified `%dist` tag that will make it clear that these builds were made against the ELN buildroot instead of the CentOS Stream 10 buildroot.= For example, `mypackage-5.2.26-3.el11~eln136` For the ELN portion of its lifecycle, the `epel11` buildroot will include the `eln` buildroot in its Koji tag inheritance. This means that builds against the `epel11` target will be performed against dependencies built in Fedora ELN (as a precursor to EPEL 11). The portion after the tilde (`~`) in the release field will match the current ELN buildroot number as defined in the `eln-build` Koji tag as `%{eln}`. This allows us to perform rebuilds by bumping the buildroot number without needing to push a new commit to each package. Shortly before the release of CentOS Stream 11 / EPEL 11, a mass-rebuild will be performed against the EPEL 11 packages, having removed the ELN buildroot from the tag inheritance. At this time, the modified `%dist` tag will be replaced with the standard tag for EPEL 11: `mypackage-5.2.26-3.el11_0`. ### Dependencies * ELNBuildSync needs to be enhanced to build against more than one target. Currently, it listens for tag events into the Rawhide tag (meaning that Bodhi has signed, tested and approved the package for inclusion into Rawhide) and then queues it for rebuild against the `eln` build target if it is part of the ELN or ELN Extras package sets as defined in the [Content Resolver](https://tiny.distro.builders). EBS will need to maintain separate targets for ELN packages and EPEL packages.