[Yum] yum.conf

[seth vidal]

On Mon, 2002-06-17 at 12:42, Robert G. Brown wrote:
> A suggestion:
> 
> Put a very simple yum.conf suitable for Duke in the man page OR comment
> out the updates and finished sections in the distribution rpm.
> 
> Both the [updates] and [finished] sections will cause yum to fail even
> if pointed at e.g. install.dulug.duke.edu/pub/linux/updates (a
> reasonable guess).  It is also hard to see what they are for from man
> yum.conf, and whether or not yum will work without them.  Might be nice
> to add a comment or two regarding purpose, at least...
> 
> Empirically, 
> 
> [main]
> cachedir=/var/cache/yum
> debuglevel=2
> logfile=/var/log/yum.log
> 
> [server]
> name=7.3 main
> baseurl=http://install.dulug.duke.edu/pub/linux/dulug-7.3/i386
> 
> # [updates]
> # name=7.3 updates
> # baseurl=http://install.dulug.duke.edu/pub/linux/updates/
> 
> # [finished]
> # name=dulug finished rpms
> # baseurl=http://localhost/finished/

I was planning on adding a pointer to the man page in the conf file -
sean's suggestion.

 
> seems to work locally.  I'm trying a running update from 7.2 -> 7.3 as I
> write this and it is telling me that it is getting a very long list of
> .hdr files, so I presume that it is working.  It'll take a while to know
> for sure over a DSL line...;-)


the stock distributed yum doesn't need a duke-specific conf file. The
one in the dulug distro has a duke-specific conf file, though.


Icon did a 7.1 -> 7.3 upgrade this weekend, and excluding a few hiccups
had few problems.

-sv

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: This is a digitally signed message part
Url : http://lists.baseurl.org/pipermail/yum/attachments/20020617/69c7a35b/attachment-0001.pgp