At 10:07 AM -0800 3/9/02, Justin Erenkrantz wrote: >On Sat, Mar 09, 2002 at 11:34:58AM -0500, Jim Jagielski wrote: >> Putting absolute paths in the config file is a Bad Idea. Using >> relatives, the entire Apache install location can be self-contained >> and easily moved by changing one line. > >How would you deal with: > >./configure --prefix=/opt/apache --sysconfdir=/etc/apache \ >--localstatedir=/var/apache > >You can't use relative path names in this case. As I pointed >out, there are several common layouts in config.layout that have >a disjoint sysconfdir or localstatedir. -- justin
I must be misunderstanding the debate. Obviously for those that use config.layout layouts, then they will require that their httpd.conf file match with how things were build. Is the question then should configure build an appropriate httpd.conf file? My own POV is that I think it's pretty bogus hardwiring such paths into an executable. They are best done with a config file. After all, Apache *does* require a config file. Why this stuff couldn't be best handled at that level is beyond me. -- =========================================================================== Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "A society that will trade a little liberty for a little order will lose both and deserve neither" - T.Jefferson
