Hey, what you want is pkgpolicy...from the man page:
pkgpolicy=[newest|last]
Default: newest. Package sorting order. When a
package is
available from multiple servers, newest will install the
most
recent version of the package found. last will sort the
servers
alphabetically by serverid and install the version of the
pack-
age found on the last server in the resulting list.
If you
don?t understand the above then you?re best left not
including
this option at all and letting the default occur.
--Chris
On Tue, 2005-02-22 at 10:24, Alan Hagge wrote:
> Hopefully the issue with this should be obvious...I don't want to have
> to modify (or have my less-familiar co-workers modify) and push to 100+
> clients a modified config file every time we override a package provided
> by a repo with one of our own. Also, if we add a new repo, we don't
> want to have to comb through what it provides to check whether it's
> providing the same things that our "custom" repo is providing in order
> to tweak include/exclude settings. I just want to be able to say "if
> this repository provides a package, its version overrides all others,
> including newer versions".
>
> Any other options?
>
> seth vidal wrote:
>
> >>Have you thought of using exclude=pkgname in the freshrpms.repo to
> >>exclude the packages that you don't want from their servers?
> >>
> >>
> >>
> >
> >As another option you can put:
> >includepkgs=pkgname1 pkgname2 pkgname3 etc etc etc
> >
> >in any repo section in your yum.conf and yum.repos.d/*.repo files.
> >
> >that will make ONLY those packages accessible from those repositories.
> >
> >-sv
> >
> >
> >_______________________________________________
> >Yum mailing list
> >Yum@xxxxxxxxxxxxxxxxxxxx
> >https://lists.dulug.duke.edu/mailman/listinfo/yum
> >
> >
> >
> _______________________________________________
> Yum mailing list
> Yum@xxxxxxxxxxxxxxxxxxxx
> https://lists.dulug.duke.edu/mailman/listinfo/yum
