On Wed, Aug 29, 2007 at 12:34:52AM -0400, seth vidal wrote: > > On Tue, 2007-08-28 at 11:07 -0500, Michael E Brown wrote: > > Questions: > > -- I currently use exclude_hook as that seems to run about where I > > need. The only other hook that runs about when I want is the > > postreposetup_hook. > > > > Why not use preresolve? > Exclude doesn't mean there will necessarily be a transaction at all. > preresolve does suggest that more to me.
Pre-resolve hook never gets run unless there are actual updates (at least in my testing.) The only place where I saw that looked logical to put it was either in postreposetup or exclude, both of which get run even if there are no other updates. > > Also you may want to only add these pkgs if the transaction has any pkgs > being installed or updated. That is effectively what happens if I put it in the preresolve hook (I'm guessing, I never had any packages being installed, so I never saw preresolve hook run.) I dont really want that, though. If the user runs "yum update" and there are new firmware types available, I would like them installed. This is applicable in a few cases: 1) Initial install of firmware-tools: user doesnt have any firmware packages installed, I want to be able to tell users to just run "yum upgrade" and it automatically gets all your firmware. 2) User installs new hardware: want the next time they run yum upgrade to automatically pick up the new hardware and pull down firmware packages that are available. 3) We create a new firmware update package for a type of hardware that didnt previously have an update package. In this case, want this to get automatically get picked up rather than having to tell all users to explicitly ask for them. So, my question becomes: does this make sense to you? I want this to integrate in a manner that you as the yum developers would expect. My end-goal is to eventually have this installed on all Dell machines going out the door. (to replace all the firmware-update methods we currently have.) To be clear, I'm nowhere close to this goal, but that is what I'm trying to design. > > -- will this work with yum 2.4 as distributed in Centos 4? I dont have > > a test machine handy and need to support back to yum 2.4. > > conduit._base.install(name=pkg.name) isn't support in 2.4 plugins. It's > actually a damn bit harder on 2.4. install() wasn't around until 2.6 Ok. This is not the end of the world, but it makes Centos 4 harder to support. :( Thanks for the feedback. -- Michael _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
