Elias Persson> > On 2014-05-05 23:19, Mattieu Puel wrote: > >>I think this is the wrong approach. If the repos are of 'questionable' > >>quality for every day use then they should be disabled (enabled=0) in > >>the repo file. > >> > >>If you want to use them manually (which from what I understand is why > >>Mattieu wrote the patch?) they should be enabled with the yum > >>--enablerepo option. ie: > >> yum --enablerepo=dogerepo install wow much-broken > >> > >>If seems like the patch / new feature is more to add a broken workflow > >>to autoupdate. > > > >Mmm, this may be a broken workflow, or at least a non-academic one :) > > > >The point is that the sysadmins which install servers and ensure that > >the base OS is up to date are not the same people than the one installing > >services on top of the base OS and managing it. > > > >Those services admins thus may install new repositories and sysadmins > >cannot be sure that those repositories are disabled (which I agree would > >be the right approach). > > > > This can be solved with the current version. > > Create dir with copies of and/or links to approved repo-confs. > Create yum.conf pointing reposdir at the prepared dir. > Config yum-autoupdate to use the prepared yum.conf. Agreed, that's a good way to do that. I still think that ENABLEREPO is as relevant as EXCLUDE configuration option (that also could be adressed with the yum configuration file). Thanks for the help and the trick anyway, I will avoid to maintain an extra patch. Cheers, -- Mattieu Puel Sysadmins team manager IN2P3 Computing Centre http://cc.in2p3.fr +33 (0)4 78 93 08 80