SCIENTIFIC-LINUX-DEVEL Archives

March 2005

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:
Jaroslaw Polok <[log in to unmask]>
Reply To:
Jaroslaw Polok <[log in to unmask]>
Date:
Tue, 1 Mar 2005 15:22:21 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
John Franks wrote:
> On Tue, 2005-03-01 at 01:48, Jaroslaw Polok wrote:
> 
>  > >   yum.cron - keep it the same or redo it?
>  >
>  > - What about using up2date (from FC3) with yum
>  >    repositories behind ?
>  >    (there are some goodies there: alike selecting
>  >     'nearest' repository server .. etc)
>  >
> 
> Yum is nicer for scripts (e.g. cron jobs) than up2date.  

Configuring up2date to use yum repository does not remove yum...

> FC3 allows the
> use of yum or up2date and I much prefer yum.  Yum will also
> automatically select a repository (based on some unknown [to me]
> algorithm).  

So will up2date using yum backend (this is done by the same script)

It took me a while to discover how to turn this off and use
> my own choice of repository.  Of course both yum and up2date are
> available and you can take your pick.

That's my point: using up2date is 'natural' for all past
Red Hat users (and a lot of current Fedora Core ones).

> Since I have about 50 SL machines I keep a local mirror of the part of
> the SL repository we use.  For that reason I would prefer that
> /etc/yum.conf not be overwritten on an upgrade.  Of course, I may be in
> the minority on this.

That's separate question: yum.conf is supplied via
yum-config RPM and should be marked there as %config(noreplace)

Cheers

Jarek

ATOM RSS1 RSS2