Package: apache
Version: 1.3.29.0.1-3
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i know that managing the list of loadable modules and package-related
apache configuration settings is a rather difficult thing to do, and i
think that it's caused headaches for package maintainers and users
alike.
so i'm wondering, is there any reason not to use a conf.d approach
for apache? you could say something like
Include conf.d/*.conf
in httpd.conf, and then all a package has to do is drop a file in
/etc/apache-*/conf.d and reload the web server. no modules-config
(which has a misleading name anyways), no wwwconfig, no maintainer
scripts mucking with users config files.
what do you think?
sean
- -- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux sativa 2.4.21-sativa #1 Sun Sep 7 23:08:55 EDT 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages apache depends on:
ii apache-common 1.3.29.0.1-3 Support files for all Apache webse
ii debconf 1.4.7 Debian configuration management sy
ii dpkg 1.10.18 Package maintenance system for Deb
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libdb4.1 4.1.25-16 Berkeley v4.1 Database Libraries [
ii libexpat1 1.95.6-6 XML parsing C library - runtime li
ii libmagic1 4.07-2 File type determination library us
ii libpam0g 0.76-15 Pluggable Authentication Modules l
ii logrotate 3.6.5-2 Log rotation utility
ii mime-support 3.24-1 MIME files 'mime.types' & 'mailcap
ii perl [perl5] 5.8.2-2 Larry Wall's Practical Extraction
- -- debconf information excluded
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAGFCxynjLPm522B0RAkJGAKCBDQgSBA0udKNOBgkmIg9kiiiihQCggUzp
XXuO4Adsmv06NOvJHh7ruMw=
=y560
-----END PGP SIGNATURE-----
