SCIENTIFIC-LINUX-DEVEL Archives

March 2007

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Maillling list for Scientific Linux developers worldwide <[log in to unmask]>
Date:
Thu, 15 Mar 2007 16:41:19 -0500
MIME-version:
1.0
Reply-To:
Troy Dawson <[log in to unmask]>
Content-type:
text/plain; format=flowed; charset=ISO-8859-1
Subject:
Re: yum-conf format
From:
Troy Dawson <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-transfer-encoding:
7BIT
Comments:
To: Karanbir Singh <[log in to unmask]> cc: [log in to unmask]
Parts/Attachments:
text/plain (21 lines) 
Karanbir Singh wrote:
> 
> Considering everyone has moved to including the yumconfigs in the 
> -release package, I wonder why you are still shipping alternate yumconf 
> packages?
> 
> - KB

Everyone hasn't *moved* to including the yum configuration in the main 
release package, it's always been that way.  And we've always pulled it 
out.  It's been that way since yum 1.0.
And I've always wondered why people put it in the main package of yum. 
Yes, yum has to have a yum-conf in order for it to do anything, but why 
replace an entire program, just to change it's configuration file.
Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI DSS Group
__________________________________________________

ATOM RSS1 RSS2