> > The situation that you are trying to protect against is most likely not > > standard. My question, is why isn't your automation just copying the > > whole conf/ directory? > > Keep in mind that I'm like the proverbial canary in the coal mine. If the > canary suddenly keels over when entering the mine, there's not much point > in > lecturing it to get more exercise, eat healthier, etc. > > I believe that the way make install in HEAD works with conf/ is > satisfactory.
I don't, but I am not going to argue anymore. I will simply say that the way things work now, I am going to have a bunch of useless files sitting in the conf/ directory of all of my production machines, because every time I upgrade Apache, I will get all of the files that I have deleted before. The conf/ directory is mine as a user. An initial installation copies some default files around, because that is nice for us to do. Subsequent installations should leave the directory alone, because that directory is mine. The same way we leave the cgi-bin, htdocs, and error directories alone. The only thing an upgrade should do, is to touch binaries and manuals. Everything else is owned by the user. Oh well. Ryan
