Burt Holzman wrote:
> Troy Dawson wrote:
> 
>>>>>> On Tue, 2005-03-01 at 01:48, Jaroslaw Polok wrote:
>>>>>>
>>>>>> > >   yum.cron - keep it the same or redo it?
> 
> 
>> I just worry that some people might think it's overly complicated.  
>> Plus there are some other changes I wanted to make.
> 
> 
> Troy,
> 
> As some other users have indicated, it's a bit confusing to have the yum 
> servers in two separate config files for either interactive (yum.conf) 
> or automated (yum.cron.*) use.   If it can be configured to use a single 
> file for both purposes, that would be ideal.  (If this already exists, 
> chalk this message up to my ignorance, but send me the proper way to 
> configure things!)
> 
> - B

Hi,
Well, in the alpha we released, it was the same old way.
I have already re-written it to use the same config file(s) that the 
regular yum does.  This because of the change to yum 2.2, and it's new 
way of doing config files.  So this should be in the next alpha/beta 
release.

With yum 2.2 you can either have it the old way, where everything is in 
just the one yum.conf file, or you can use a /etc/yum.repo.d/ directory. 
  In that directory you have repo file's, where you just put one 
repository in each file, and each repository can have it's own features, 
such as 'enabled'.  (Or you can have some combination of the two)

Anyway, with the new yum.cron, it will create it's own yum.conf head 
(the [main] section of the yum.conf) that basically just has the 
'excludes' stuff in it, and then it will use whatever repo's you have 
enabled in your yum.repo.d directory.

So it will basically be just like doing a 'yum update' except that it 
will have the excludes in it.

Er... looks like I was rambling a bit.  Hope that clears things up 
instead of confuses things.

Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________