James Tait <[EMAIL PROTECTED]> writes: > FWIW... I, as a user, agree wholeheartedly with this approach. If > I've taken the time out to write web pages then I don't want them > clobbered when I upgrade Apache. In the same way, if I've taken the > time out to configure Apache the way I want it, I don't want that > configuration clobbered when I upgrade.
nothing is getting clobbered > Nor do I want spurious -std > files copying in there to confuse matters. Some of us want the -std files though. From time to time I (and potentially many other people who start with Apache's basic httpd.conf) compare httpd.conf and httpd-std.conf to see if I want to merge in some of the Apache changes. I don't think anybody would be in favor of not providing httpd-std.conf; perhaps the issue is just where to put it when the user does an install (from binbuild or from make install it should work the same). -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
