EPEL, the Ultimate Answer | Fedora Podcast Ep. 42

Almost every RHEL or CentOS Stream admin ends up leaning on EPEL eventually, usually without thinking too hard about what it actually is or who keeps it running. In episode 42 of the Fedora Podcast I sat down with Carl George, who leads the EPEL team, and Adam Samalik from the CentOS Stream side to fix that. We got into what EPEL is for, why it has the reputation it does, and what’s changing with the move to EPEL 10.

A few things worth carrying away from the conversation:

• EPEL’s whole reputation rests on one rule: it only adds packages, it never replaces what ships in the base OS. That single constraint is why so many admins who won’t touch a random third-party repo will happily enable EPEL in production.
• EPEL 10 rethinks the model to track each RHEL minor version instead of a single moving target, folding in the lessons from the old “EPEL Next” experiment. The payoff is that the team can get ahead of a RHEL release rather than scrambling at each beta.
• Getting involved is far more approachable than people assume. If you can package for Fedora, you can already help EPEL — and even leaving QA “karma” on updates in Bodhi moves packages toward stable faster.

If you run anything downstream of Fedora, this one’s worth the time.