On Wed, Aug 29, 2007 at 10:49:43AM -0400, James Antill wrote:
> On Tue, 2007-08-28 at 20:38 -0400, Matthew Miller wrote:
> > On Tue, Aug 28, 2007 at 11:07:53AM -0500, Michael E Brown wrote:
> > > The intent of this yum plugin is to eliminate this bootstrap as a
> > > separate step. The intent is that whenever the user does a yum upgrade,
> > > that if there are any new firmware packages in the repository that were
> > > not previously on their system, they will get automatically
> > > bootstrapped.
> >
> >
> > Shouldn't it only do this if an option ("--check-new-firmware", or
> > something) is given? When I'm applying security updates is the last time I
> > want random new hardware support installed.
>
> I think maybe a more obvious change is to only add the fireware
> packages if the user has done "yum update" without any package name
> arguments (or with arguments that match the firmware package names).
This sounds fine to me. Can you suggest how I might accomplish this from
my plugin?
> The security plugin will do the right thing, as on an update it runs
> from preresolv (which is after the packages are added in exclude).
> However AIUI some of the other "exclude plugins" just run from the
> exclude hook, so they'll be in a race to see who wins.
I understand that. The only two hooks that look like they solve my
problem are postreposetup and exclude. The problem is that postreposetup
looks like it runs before new metadata is downloaded. So, exclude looked
like the only hook that really did what I needed.
What is the nature of the other exclude plugins? Are they something that
the user is likely to see as a problem? The two plugins that I see that
use exclude_hook are protectbase and priorities. I dont see my plugin
doing anything that would really interfere with these two.
--
Michael
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
