SCIENTIFIC-LINUX-DEVEL Archives

May 2014

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Elias Persson <[log in to unmask]>
Reply To:
Elias Persson <[log in to unmask]>
Date:
Tue, 6 May 2014 13:22:03 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
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.

ATOM RSS1 RSS2