[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: FC5 and Yum Plugins

On Fri, Dec 30, 2005 at 01:27:33AM -0800, Jesse Keating wrote:
> On Fri, 2005-12-30 at 01:17 -0800, Jarod Wilson wrote:
> The question is, what good is this plugin doing?  If you enable a
> 3rd party repo, to get something like MythTV, you'll need to get the
> deps.  If the deps happen to replace core/extras packages, then they
> do.  They are necessary for the software you are asking to install.
> So you're going to override it to install your software.  This is in
> the install context.  In the update context, then sure if the 3rd
> party repo nvr for a package is higher than the nvr for the
> core/extras package then this plugin might be useful to ignore that,
> unless ignoring would break deps with something like MythTV.  Seems
> to me that there should be a different method than just protecting
> core/extras.  Seems the 'protection' should be based around
> replacing for no other reason than nvr comparison.  If the
> replacement is pulled in for an honest dep satisfaction, rather than
> just a higher nvr comparison, then it should be allowed.

How would you do that w/o checking the specfile itself? If package foo
from core is replaced with foo compiled with different build options,
or a bugfix that is required in a context not interesting in core (so
it will not make it into "updates") or similar, how can you
distinguish it from arbitrary package updates?

> Otherwise prompt user or block.  This keeps 3rd party repos working
> properly and keeps users systems as close to strict core/extras as
> possible w/out breaking user installed software.
Axel.Thimm at ATrpms.net

Attachment: pgpSaHWHztwEu.pgp
Description: PGP signature

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]