Bug#676975: apache2.2-common: contradictory comment in /etc/apache2/apache2.conf about the .load suffix
On 2012-06-11 00:10:39 +0200, Arno Töll wrote:
> Hi,
>
> On 10.06.2012 23:49, Vincent Lefevre wrote:
> > /etc/apache2/apache2.conf has the following comment:
> >
> > # Yet we strongly suggest that all configuration files either end with a
> > # .conf or .load suffix in the file name. The next Debian release will
> > # ignore files not ending with .conf.
> >
> > If only files ending with .conf will be taken into account in the next
> > Debian release, then the suggestion shouldn't mention files ending with
> > the .load suffix.
>
> I can see how this is a bit misleading, but I think one /could/
> understand what I meant to say. Currently we follow the inclusion rules
> as denoted in apache2.conf. That is, we include
> /etc/apache2/mods-enabled/*.(conf|load), but we do include
> /etc/apache2/sites-enabled/* and /etc/apache2/conf.d/* with the noted
> exceptions.
>
> In 2.4, that's supposed to enter Wheezy+1 we will change this to include
> /etc/apache2/sites-enabled/*.conf and /etc/apache2/conf-enabled/*.conf
> only, with the module inclusions left untouched.
>
> Let's make a shortcut and let me know if you have a better formulation.
> That way we might come over this recurring loop. ;-)
I'm not sure I've understood. You meant that 2.4 will still include
/etc/apache2/mods-enabled/*.(conf|load)? Then...
# Yet we strongly suggest that all configuration files either end with a
# .conf or .load suffix in the file name. The next Debian release will
# ignore files not ending with .conf (except for mods-enabled).
or
# Yet we strongly suggest that all configuration files either end with a
# .conf or .load suffix in the file name. The next Debian release will
# ignore files not ending with .conf (nor .load for mods-enabled).
Another change that should be done:
# * Configuration files in the conf.d directory are either provided by other
# packages or may be added by the local administrator. Local additions
# should start with local- or end with .local or .local.conf to avoid name
# clashes. All files in conf.d are considered (excluding the exceptions noted
# above) by the Apache 2 web server.
You should remove ".local or", because it won't work with 2.4 (if I've
understood correctly).
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: