Bill Allombert wrote: > What do you suggest ? Would checking for the config file existence be > enough ?
I think it should also take care to manually call update-menus in its postinst, to make sure its menu program runs after it's configured. > > However, thinking about it some more, packages like cdd-common were > > already broken before menu became triggerized. The breakage > > just wasn't as likely to show up, but could occur: > > > > dpkg --unpack a-game.deb cdd-common.deb > > dpkg --configure --pending > > > > IIRC dpkg --configure --pending configures in alphabetical order. So > > a-game would be confgured first, when cdd-common was unpacked but not > > yet configured. If a-game uses menu, then update-menus runs, running > > cdd-common's menu program, which would fail the same as it does with > > triggers. > > I am not saying the old system is fullproof, but update-menus was never > run before the dpkg lock was released which only happened after > 'dpkg --configure --pending' returned, at which point both a-game and > cdd-common would be configured. Ah, you're right. The scenario where the problem could occur before was thus much less likely: dpkg --unpack cdd-common.deb dpkg -i a-game.deb -- see shy jo
signature.asc
Description: Digital signature
