On Thu, 18 Jul 2002, Greg Ames wrote: | I guess I wasn't clear. I have automation that creates a new conf/, | then copies in httpd.conf* from the production conf/ with appropriate | edits. So my conf/ directory exists, but doesn't contain mime.types (or | several other files which aren't relevant on daedalus). | | make install runs after that. It used to copy in everything except the | httpd.conf file, which worked perfectly for me. Now it doesn't copy | *any* of the conf/* files because the directory exists. It would be | better if we did this on a more granular level, i.e. check to see if the | individual file exists in the target dir, then copy/don't copy as | appropriate. | | If we had a customized mime.types, I wouldn't want it to get clobbered. | I think the old code would have done that.
Apache configuration files can be pretty much considered user-land stuff that shouldnt be touched by 'make install' There are so many ways for an admin to organize his/her apache configuration files, from a flat httpd.conf to having it broken out into many Included files of arbritrary name. Not to mention custom entries in mime.types and so-forth. What may be good for you isnt necessarily good for everyone else. Keep a 'make install' over an existing installation as transparent as possible. There's no need to fix something that's not broke. If there are pertinant changes to a config directive or something else along those lines, the admins can add them to their configs after reading about them in CHANGES .... right? /dale
