On Sat, 04 Jun 2011, Bill Allombert wrote: > > But Bill, you have not replied to my proposal where menu would consider > > packages already configured once as good enough to keep the menu entry. > > Menu entries can be executable. In that case they are executed by update-menus > and the output is interpreted as a menu files. Menu must ensure that they are > only > executed when the package is configured.
Menu must ensure that they are successfully executed once. It doesn't matter that the package is configured or not. In this case, the package has already been configured once. A new version has been unpacked doesn't mean it's not working. It's highly unlikely that a new dependency has been introduced due to the executable menu entries. And even it this execution fails, you can still keep the former entry or force a supplementary run in the postinst for the subset of packages that use executables as menu entries. Much like Pre-Depends are satisfied when a good version was already configured once (even if another one got unpacked in the mean time), you do not need more than this IMO. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
