I think having a EPEL mirror in the way described by Steve is an excellent idea. It exactly parallels my own requirement (and I suppose any site's requirement) of managing updates to many machines. The only way to guarantee that you are not going to break something with an update is to test your applications on an updated *test* environment. The only way to guarantee that your *production* environment is updated in the same way as the *test* environment is to have a mirror repo that is not changing unexpectedly.
Tim Kanuka Canadian Light Source -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve Gaarder Sent: Friday, March 27, 2015 09:45 To: Akemi Yagi Cc: SL Users Subject: Re: SL7x and the 'epel' repo In that case, I'm thinking that it could be useful to maintain an EPEL mirror that does not get updated between TUV's release and the SL release. I could do that for my own use or it could be a community effort. Thoughts? Steve Gaarder System Administrator, Dept of Mathematics Cornell University, Ithaca, NY, USA [email protected] On Fri, 27 Mar 2015, Akemi Yagi wrote: > On Fri, Mar 27, 2015 at 7:47 AM, Steve Gaarder <[email protected]> > wrote: > > >> Thinking about this some more, I assume that EPEL is actually built >> against the latest from TUV, so 7.1 in this case. Correct? > > Yes, that is correct. There is a similar discussion thread on the > CentOS mailing list: > > http://lists.centos.org/pipermail/centos/2015-March/150945.html > > Akemi >
