Please leave mods-enabled alone!

[Adam Warner <lists@consulting.net.nz>]

Hi all,

I'm writing to this mailing list because I suspect the symlinking to
mods-enabled problem is more widespread than with just the
libapache2-dav-svn package.

I am happy for libapache2-dav-svn (0.24.1-1) to created a new file
/etc/apache2/mods-available/dav_svn.conf. What is not nice is also
symlinking the new file to /etc/apache2/mods-enabled/, which adds a new
configuration file to a working system and is likely to duplicate or break
existing configurations. In my case configuration was already in
/etc/apache2/httpd.conf (remember dav_svn.conf didn't used to exist) so I
ended up with two places defining different locations for subversion.

It's clear to me that mods-enabled is for site-specific configuration. If
Debian developers want to add new configuration files then just leave them
in mods-available. Users can always create symlinks to mods-enabled.

Regards,
Adam