Arno Töll <[email protected]> writes: > I'm finally coming back to the dh_apache issues you filed long ago.
>> I believe you should therefore just remove this conditional and run this >> code in postinst unconditionally. > Your explanation sounds right to me. However, we do not unconditionally > disable the module either. We only do so in case of postrm purge|remove > to ensure the web server is not reloaded without need. This makes the > abort-upgrade|abort-remove|abort-deconfigure operations a no op with > respect to Apache maintainer scripts. Ah, yes, I see. You only remove the module during postrm, so this would only affect people who wrote explicit maintainer scripts to do something to the module during prerm. (I think there was a comment in apache2-maintscript-helper to that effect.) Given that, I agree, there's no need to run on any action other than configure unless you want to cater to people who are fiddling about in prerm, and I don't see any reallly obvious reason why you should need to do that. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
