[CentOS-devel] EPEL 7 in Extra Repo

> On Jul 7, 2014, at 21:24, Jim Perrin <jperrin at centos.org> wrote:
> 
> 
> 
>> On 07/07/2014 08:19 PM, Peter wrote:
>>> On 07/08/2014 01:10 PM, Nico Kadel-Garcia wrote:
>>> Thanks for all the work! I've some personal experience of shifting to
>>> major new releases, and the adventures involved in re-engineering the
>>> build environments for compatibity. You've my sympathy.
>>> 
>>> Would it make sense to have a "yum-conf-epel-release-beta", to be
>>> obsoleted by  an upcoming "yum-conf-epel-release"? It's an important
>>> repo for "mock" and a number of Perl modules, at least for me. I'd be
>>> happy to submit a spec file in a day or two, if it would help.
>> 
>> Yeah, whatever will we do without the package in extras?  I mean how did
>> anyone ever manage to install EPEL in previous releases of CentOS?
> 
> Really? Didn't I *just* go on a mini-rant about this 12 hours ago?

??? I was polite, I offered code. It's also the model that works well for Scientific Linux, where their automatic configuration for third party repos works quite well.

> 
> If you really want to do this, you have to take a lesson from Chris
> StPierre and be willing to go all the way with a full-blown
> profanity-laden diatribe. This is hardly worth it.

But... I like you folks. And you asked nicely for me to be less aggressive.


>> Ok, all sarcasm aside:

Ahh. Sarcasm... I'd not always clear. 

>> yum --nogpgcheck install
>> http://dl.fedoraproject.org/pub/epel/beta/7/x86_64/epel-release-7-0.2.noarch.rpm

Which, I'm afraid, is an unstable URL. Even if the 'beta' location remains consistent, EPEL discards old RPMS rather than keeping them in their repo. So it can be guaranteed to break in the near future.

"yum install yum-conf-epel-release", however, would distinguish the CentOS configured access from the epel-release RPM provided by EPEL themselves. It seems to work well for Scientific Linux, and I've found it very useful, even on otherwise pure 'CentOS' systems.

Thanks to the team for planning to directly enable EPEL access, in any case. It's one of those pesky post-kickstart steps on all my systems that I'd prefer to just include among the selected packages.