On Tue, 2005-11-29 at 07:21 -0800, Bryan J. Smith wrote:
> Johnny Hughes <mailing-lists@xxxxxxxxxxxx> wrote:
> > The new protectbase plugin (currently in testing):
> http://lists.centos.org/pipermail/centos-devel/2005-November/000947.html
> > will also help with the issue of third party repos updating
> > core components.
> > If you use this plugin and set all the centos repos to:
> > protect=1
> > and set your 3rd party repos to
> > protect=0
> > You will prevent upgrades of core components ...
>
> Excellent! I did not know about this YUM plug-in. Yet
> another thing to go into the generic Enterprise Linux
> Manager's FAQ yet to be released.
>
> > This might cause an error IF a core component HAS to be
> > upgraded to meet a valid dependency ...
>
> But as long as it causes an error, I know about it. That's
> fine by me, I can manually resolve things in such cases.
>
> > but then you could manually do those and exclude
> > them from the core centos repo ... and from that point
> > forward, get those from the 3rd party repo.
>
> Exactly. Is there any chance that the plug-in won't catch
> something? Or is it pretty absolute, and will always error
> out?
>
> Again, that's the desired result I want. I don't want it
> blindly replacing core repository packages.
It has worked quite well for me in testing ...
AS LONG AS ... you remember to set protect=0 for 3rd party apps.
I think protect=1 is assumed if you don't have anything listed for the
3rd party repo ... meaning it will replace core files.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.centos.org/pipermail/centos/attachments/20051129/8ccb0a0c/attachment.bin
