Using the yum-priorities plugin, you can permanently enable
repositories, set at a lower priority.  Furthermore, for specific
packages you can force the higher priority repositories to exclude them
so they are caught by the lower priority auxiliary repos (epel,
rpmforge, etc).

http://wiki.centos.org/PackageManagement/Yum/Priorities

For example, in a CentOS-Base repo I had the following config to get
Subversion 1.6 from rpmforge:
priority=1
exclude=subversion

Then in the rpmforge.repo file
priority=3
# for some reason I was blocking nagios from this repo.
# Probably unnecessary since it had a lower priority than epel.
exclude=nagios*

I think for this setup I also had EPEL as priority 2, excluding
subversion from there as well.

So it works like this:
The priority 1 repositories are checked for updates, and anything not
explicitly excluded gets updated.  Then the other repositories are
checked sequentially for updates to the packages excluded from the
higher priority repos.

+++++++++++++++++
Michael Berkowski
Linux Systems Administrator and Programmer
Minitex - University of Minnesota
PGP Public key:
http://www.tc.umn.edu/~berk0081/pgp/pubkey.asc
+++++++++++++++++

On 10/7/2011 9:01 AM, gregrwm wrote:
> used to be you had to be careful to only enable dag/epel/atrpms/kde-redhat long enough to get something specific,
> and have them disabled when doing yum update.  i presume this is still important, or at least good practice.
> 
> once you've installed, for example, nagios, and it pulls in some addidional packages from dag/epel,
> you of course want to keep everything up to date at all times.  i'm guessing it's insufficient to just do
> 
> yum --enablerepo=dag --enablerepo=epel install nagios nagios-plugins
> 
> without now also explicitly mentioning those additional packages, in case nagios doesn't have an update but some of the addidional packages do, am i right?
> 
> please clarify whether your answers are applicable to rhel/centos/SL/dag 6/5/4 yum.
> 
> pointers to clueful writeups especially welcome.
> tia,
> -g
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> tclug-list at mn-linux.org
> http://mailman.mn-linux.org/mailman/listinfo/tclug-list

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20111007/4e2123ba/attachment.pgp>