After an install, the default config files are useful. After an upgrade

they aren't.

If the config directive's syntax changed, Apache will tell
you which one changed, and the docs are a better place to go for details
then the default config files.  BTW, the syntax of a directive hasn't
changed for a VERY long time.

If the semantics changed, then nobody will ever know that they need to
look in the default config files to determine that they semantics changed,
because there is no error message.

The argument that you want to be able to get the defaults back doesn't
hold water, because 99.9% of all admins backup their files before
modifying them.  If you aren't backing them up, then that is your problem.

The argument that you may not have a full config directory also doesn't
hold water, because the assumption is that the conf/ directory is coming
from a working server.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@96157 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/STATUS b/STATUS
index 4e717abd44e1c92df114281242199bcb07ac862a..65d1cbc281f7a764fec433083ea9a0d802043c5a 100644 (file)
--- a/STATUS
+++ b/STATUS
@@ -1,5 +1,5 @@
 APACHE 2.0 STATUS:                                              -*-text-*-
-Last modified at [$Date: 2002/07/23 17:24:35 $]
+Last modified at [$Date: 2002/07/23 17:44:55 $]
 
 Release:
 
@@ -76,6 +76,10 @@ CURRENT VOTES:
          sysconfdir/examples or manualdir/exampleconf/
          +1:   slive
 
+      d) Installing a set of default config files when upgrading a server
+         doesn't make ANY sense at all.
+        +1:   rbb
+
     * apachectl should revert to just being an init script and
       httpd.sh should be the wrapper for httpd which sources envvars
       and allows any options to be passed through