Actually, before Josh drops this into the 'Won't Consider' pile, I wanted to point out that this feature is 1) very new, and 2) possibly incomplete on some platforms.
I'd expect our measure of processing (or excluding) files from a conf directory should probably match up with other daemons which accept conf directories. It seems like the number of OS-specific exceptions implies that we aught to create a build-time directive to add additional excluded-name patterns. I expect any file starting from dot or ending with ~ aught to be excluded across platforms. But if you are bundling Apache for .rpm... then you would build it to --exclude-conf-match=\.rpm or something like that. That's my goofey idea of the morning. At the very least, was 2.0 patched when this argument came up last time and improved on 1.3? >Patch that avoid reading some files from configuration directory >(../httpd.conf/): >- starting from dot >- ending with ~ (backup copies) >- ending with .rpmsave, .rpmnew, .rpmorig > >These files rather shouldn't be processed because such files are left after >editing/instalation/deinstalation of rpms etc... >------- Additional Comments From [EMAIL PROTECTED] 2002-04-14 20:54 ------- >Unfortunately, you have just enumerated files coming from a couple specific >programs (emacs, rpm). That is really not general enough to be very useful. >There are tons of other file types that someone may want to exclude. > >I think someone once created a patch that would allow something like >Include conf/*.conf >A patch like that might have more chance of acceptance. Your particular patch >isn't going to be accepted, but thanks for the contribution.
