On Sun, Mar 30, 2008 at 04:06:15PM -0400, Joey Hess wrote: > The attached patch makes menu support triggers, as implemented in dpkg > in (currently) experimental.
Hello Joey, Thanks a lot for your patch and analysis. My comments: > - Adding a --real option to update-menus. This can be used to force a > real update-menus run even if dpkg is running. It should only be > needed to be used by menu internally. Given the above, I have renamed it to --trigger and did not documented it yet to avoid breaking translations. > - Adding a "triggered" action to the postinst, which runs update-menus > --real. This is called by dpkg when menu is triggered. > I didn't add trigger support for menu-methods files. It would probably > be possible to add that, but since there are not a lot of them, it > didn't seem worthwhile at this point. Packages with menu-methods can run > update-menus as usual. What would be the cost to add /etc/menu-methods to debian/triggers ? Do conffiles release triggers ? There are about 55 menu-methods. > So there's a stage 2 to this transition -- once stable has a dpkg that > supports triggers, packages can stop running update-menus in their > maintainer scripts. (Unless they have a menu method.) Installation of > such a package will look like this: Personnaly, I would prefer to delay the stage 2 after the release of lenny. This way partial upgrades are not broken (i.e. menu version is kept at etch, but some packages are upgraded to lenny). Also, there are pending menu transitions I like to finish before staring a new one. > Later on, some simple changes to apt, to make it use > --suppress-triggers, can actually bring the number of update-menus runs > per apt run back down to 1. (See #473461) This would be good, because the 'two second' sleep prevented most of those spurious update-menus runs. update-menus can be slow if the menu-methods are slow (e.g fvwm-crystal) and some people (me...) have all the 55 menu-methods installed. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
