Package: apache2.2-common
Version: 2.2.16-3
Severity: wishlist
I noticed several bugs (#565738, #553173, #604980) complaining more or less
about the same thing: URL namespace pollution by packages placing configuration
snippets into /etc/apache2/conf.d/.
As stated in /usr/share/doc/apache2.2-common/README.Debian.gz:
Files and Directories in /etc/apache2:
[...]
conf.d/
[...]
If the local administrator is not comfortable with packages
activating their config files by default, it is possible
to change the 'Include /etc/apache2/conf.d/' in apache2.conf
into 'Include /etc/apache2/conf.d.enabled/' and create that
directory. He can then put symlinks to the files in conf.d
which he wants to enable into conf.d.enabled.
So these bugs could basically get closed with a "wontfix" tag.
As the same bugreports could be filed against most of the packages putting
stuff in /etc/apache2/conf.d/: nagios, gitweb, smb2www, etc, I believe this
problem really belongs to the apache package itself.
Several options would be possible:
- include /etc/apache2/conf.d.enabled/ by default, instead of
/etc/apache2/conf.d/
- make a2enconf and a2disconf utilities
- including /etc/apache2/conf.d/ only in /etc/apache2/sites-available/default
- have a policy about what packages are allowed to put into
/etc/apache2/conf.d/
- ...
Maybe should this be discussed on debian-devel ?
Cheers,
Marc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
