I don't vote on this craziness but I've always thought the overlap of Port, ServerName, Listen and BindAddress was severely hideous so fwiw, bravo for striking Port.
My original motivation for patching the old configure script to handle --with-port was for the course I teach: I introduce students to apache by doing the minimal precompile configuration just to get something running out of the asf tarball. Then, of course, I start introducing them to all that is evil and loathsome in httpd.conf -- please, whatever you do, continue the precompile configuration behavior of enabling a working Apache. IMO, the minimal bootstrap steps should continue to be ./configure --with-port=MY_ASSIGNED_PORT --prefix=$HOME/apache make && make install cd $HOME/apache ./bin/apachectl start Ta-da! On Thu, 4 Oct 2001, Aaron Bannert wrote: > On Thu, Oct 04, 2001 at 11:43:40AM -0700, Justin Erenkrantz wrote: > > I sort of agree with Aaron about run-time configuration options, but > > not enough that I want to edit files manually. =) > > I don't want to have to edit them manually either, but I end up doing it > anyway. > > > This concept has always been a topic of debate between Aaron and > > myself - we talked about this for a long time when we did flood. > > I'd be curious to see what other people think. > > > > I think build-time options can specify the defaults - they can > > always be overriden later... -- justin > > That is the trouble with this, it is very alluring to have it all fall into > place at "make install"-time, but it's hard to see how that can be a problem > from our perspective. > > -aaron > cheers, -Ian -- Ian Kallen <[EMAIL PROTECTED]> | AIM: iankallen
