> OK. I'm convinced. At least three people have said they use this
> extensively, so we should continue to support it. Why don't we just keep
> the existing behavior and add "Include dir/*.conf" as an option. We can
> assume that people who are using recursively included directories are
> smart enough that they can avoid the backup problem on their own.
This is certainly -good enough- this is not quite as ideal as true
recursion; i.e. if you need to do an upfront
Include conf/base/*.conf
Include conf-local/${CUSTOMERID}.conf
Include conf/ssl/*.conf
Include conf/creditcard/*.conf
Include conf/excell-stock/*.conf
Include conf/php4/4.4.3-p3/*.conf
you kind of need to 'hope' that the directories are 'there'; or risk
errors/supress errors.
Bear in mind that a lot of folks try to reconfigure without actually
changing a config file (yes - I agree - this is a bid 'odd').
But again - a *.foo include is good enough compromize for all cases I am
familliar with - but would like to stress that a recursive include can
make live easer. (but so could true XML as a config file; a
mod_ldap_config and half a dozen other things).
Another compromize may be to make 'Include' or 'IncludeFile' to be very
strict and a second directive 'IncludeDirectory' or
'RecurseConfigDirectory' to be very slack and suck anything in.
Dw
