Ryan Bloom wrote:
> > > You are working around a problem in your script in the Apache
> > > upgrade step.
> >
> > no sir. It would have been a piece of cake to change my perl script
> to
> > insure
> > that conf/ has enough stuff so the server can start. But I couldn't
> take
> > the
> > easy way out with a clear conscience because other people are likely
> to
> > get
> > burned in a similar manner.
>
> Come off it. That is insane. You have a broken script, fix it. Nobody
> else will get burned this way, as proof, this is how 1.3 has worked for
> years, and there were never any complaints. Anybody who has an existing
> configuration who wants to copy that config to a new server MUST copy
> all of the config files. You script didn't. That is broken. Period,
> end of story.
Let's check the proof:
[gregames@gandalf apache]$ grep "CONFIG" apache-1.3/Makefile
echo "[PRESERVING EXISTING CONFIG FILE:
$(root)$(sysconfdir)/$${target_conf}]"; \
echo "[PRESERVING EXISTING CONFIG FILE:
$(root)$(sysconfdir)/$${conf}]"; \
Actually, 1.3's make install-config works on a file-by-file basis, essentially
the same as HEAD for 2.0.
I certainly would never claim that 1.3 is perfect. But it's a pretty decent
starting point, especially when it comes to externally visible behavior.
Greg
