Ryan Bloom wrote: > > That is the difference between developers and users. I want the -std > files on my DEVELOPER machines, and I have tricks to get them. I don't > want them anywhere near my PRODUCTION machines, because they get in the > way.
You are hardly a typical user. You shouldn't think that what's good for Ryan-as-user is automatically good for *-as-user. > I would be in favor of never installing them on an upgrade. They are > useless on a production machine that already has a configuration. They > are meant as DEFAULT values to help people get up and running. And they also provide examples of how things are done. When those things change on an upgrade -- such as adding the <IfModule> wrappers -- it makes excellent sense for them to be provided. > Is there ANY other software package anywhere that actually re-installs > the default configuration files on an upgrade????? Stop handwaving. No-one is suggesting overwriting httpd.conf. And yes, *many* packages provide their defaults as part of an upgrade. Some even move the existing user config aside and put the new one in place. As an example, look for .rpmnew and .rpmsave files on a RH/MDK/... machine. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!"
