Him On 10.06.2012 23:28, Harald Dunkel wrote: > I really would prefer if apache behaves as it is described in > upstream's documentation. Their recommendation is to avoid > > Include /somedir/ > > completely, and to use something like > > Include /somedir/*.conf > or > IncludeOptional /somedir/*.conf > > to avoid conflicts with editor backups instead. Sounds > reasonable to me. A lot of other Debian packages use > *.conf for their config files as well. _And_ it gives > the user the freedom to introduce its own naming scheme. we all agree, but this can't be changed easily for legacy compatibility. This is an invasive change which can't be established without a major package transition in Debian. We have packages which do not comply with the *.conf pattern yet. We already changed this behavior for Apache 2.4, but this didn't make it in time into Wheezy for various reasons beyond our control. The Apache 2.4 upgrade will require a major transition anyway. Therefore, while being at it, we also changed this to your suggestion already. We can't just do it just now. Yet. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
Attachment:
signature.asc
Description: OpenPGP digital signature