On Sun, Dec 31, 2017 at 06:35:00PM +0000, Niels Thykier wrote: > On Sun, 13 Aug 2017 10:24:00 +0000 Niels Thykier <ni...@thykier.net> wrote: > > Hi, > > > > Reading through this bug, it occurred to me that the use-case for having > > debhelper inject the postinst script is for executable menu files.
The other use case is to prevent entries to appear in menu before the corresponding packages are configured. This is done to prevent random breakage during partial upgrades. This is an important feature and the dpkg file trigger is inadequate for that purpose, because it run before packages are configured, not after. The postinst is required to avoid packages being omitted from the menu. Raphaël comment is missing the fact that a menu entry can be shipped in package A but checks for the installation of packages B1 and B2 (the menu system has a field to cover this). > > @Bill: Would it work for you if debhelper only added the snippet for the > > menu files that are executable? To my knowledge, there are at most a > > handful of these so it would help a lot in removing postinst scripts. > Did you have a chance to review the situation and consider if the above > proposal would work for you? Given the TC decided to kill the menu system based on a misunderstanding on how the different menu systems interact, I have nothing to say. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.
