> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jeff Trawick
> Sent: 23 July 2002 19:30
[...]
> I'm curious about how other people feel about this, so I started a
> vote in STATUS.
* httpd-std.conf and friends
a) httpd-std.conf should be tailored by install (from src or
binbuild) even if user has existing httpd.conf
+1: trawick, slive, gregames, ianh
In the build tree? If yes, then sure.
b) tailored httpd-std.conf should be copied by install to
sysconfdir/examples
+1: trawick
-0: striker
Installing in ${sysconfdir} or a subdir thereof is in my opinion not
an option. If users go through the effort of keeping their config
directory clean, we shouldn't clutter it when they reinstall/upgrade
apache.
c) tailored httpd-std.conf should be installed to
sysconfdir/examples or manualdir/exampleconf/
+1: slive
Having an example config in the manual seems like a decent idea.
d) Installing a set of default config files when upgrading a server
doesn't make ANY sense at all.
+1: rbb, striker
ianh - medium/big sites don't use 'standard config' anyway, as it
usually needs major customizations
Exactly, why should users that keep their config dir clean have to pay when
some users don't want to be troubled with getting httpd-std.conf from elsewhere
and need it installed at their fingertips?
Secondly consider that you have installed 2.0.35 and are upgrading to 2.0.40.
If ${sysconfdir}/[examples/]httpd-std.conf would be overwritten, you would have
no chance to compare the old httpd-std.conf with the new httpd-std.conf anymore.
I consider that diff more usefull than the diff between httpd.conf and the new
httpd-std.conf.
Sander
