SCIENTIFIC-LINUX-DEVEL Archives

June 2010

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:
Dr Andrew C Aitchison <[log in to unmask]>
Reply To:
Dr Andrew C Aitchison <[log in to unmask]>
Date:
Mon, 7 Jun 2010 23:37:04 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (32 lines)
On Mon, 7 Jun 2010, Troy Dawson wrote:

> This brings up a thought that I was having.
> 1 - Switch from having a yum-conf rpm to having the default yum repositories 
> in sl-release, like the rest of the world.
>
> 2 - Remove all of the non-sl repositories out of the default yum repositories 
> (dag, atrpms, adobe), and then have *all* non-sl yum repositories in their 
> own rpm.
> 2a - We could name these yum-conf-<repo> such as yum-conf-dag, 
> yum-conf-elrepo and yum-conf-epel.  But I'm up for giving them a different 
> name if everyone thinks something would be better.

I'm not sure there is an advantage to having them all in separate
packages, given that installing one of these package does *not*
mean that I want to enable it by default.

> 3 - Have the yum priorities plugin installed by default, and all yum 
> repositories need to have a priority ranking.

That might not be sufficient. I'm thinking of packages like clamav
with multiple rpms. Considering packages whose names include clam,
epel and rpmforge have eight packages with the same names.
In addition epel has another eight packages and rpmforge another two.
It might not be too hard to tangle onself up by installing say
clamav-data instead of clamav-db, or switching which has the higher
priority then trying to update clamav.

-- 
Dr. Andrew C. Aitchison		Computer Officer, DPMMS, Cambridge
[log in to unmask]	http://www.dpmms.cam.ac.uk/~werdna

ATOM RSS1 RSS2