Package: apache2-dev Version: 2.4.2-2 Severity: wishlist Some Apache modules require global configuration for which there is no reasonable defaults, and therefore require that the local administrator do the configuration before the module can be enabled. Currently, those modules require either doing something moderately complex in the maintainer scripts using --conditional or disabling dh_apache2's maintainer script handling with -n (and thereby losing the postrm handling, for which the default behavior would be fine).
A nicer mechanism would be to allow the *.apache2 configuration file have an option for mod *.load lines saying not to enable the module by default. If the module is enabled, then Apache should still be restarted on upgrade (or other configuration actions). If the module is not enabled or wasn't previously installed, nothing should be done by default in postinst. The postrm handling would remain the same. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apache2-dev depends on: ii apache2 2.4.2-2 ii debhelper 9.20120608 ii libapr1-dev 1.4.6-3 ii libaprutil1-dev 1.4.1-2 ii openssl 1.0.1c-3 ii perl 5.14.2-12 apache2-dev recommends no packages. apache2-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120714030647.18841.80189.report...@windlord.stanford.edu
