httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sander Striker" <>
Subject RE: Having sane default configs was Re: cvs commit: httpd-2.0 STATUS
Date Sat, 09 Mar 2002 19:07:39 GMT
> From: Thom May []
> Sent: 09 March 2002 19:45

> * Aaron Bannert ( wrote :
>> On Fri, Mar 08, 2002 at 04:12:39PM -0500, Rodent of Unusual Size wrote:
>>> Let me clarify: By putting absolute paths into the config
>>> files, we are locking the installation into a single location.
>>> By using ServerRoot-relative locations, as we always have, the
>>> installation can be moved around the filesystem, or even to
>>> another box.
>>> Now, if the $foodir values can be defined as ServerRoot-relative,
>>> at least for some layouts (like the default), then I'm of
>>> the other opinion, and +1 on the idea.  But absolute paths?  No way!

Well, I think that we can't guarantee relative paths in all cases, but
we can in the case of --prefix without --layout and in some cases of

>> Thom and I have had to deal with this lately and came up with a couple
>> of m4 macros to help:
>> APR_EXPAND_VAR takes a variable and recursively interpolates the contents.
>>   Useful for when datadir='${foodir}/bar'.
>> APR_PATH_RELATIVE takes a path and a prefix var and strips off the prefix
>>   (and any extra / characters) if they share a common prefix, else it
>>   takes the literal of the original path.
>> I'm thining that to deal with apachectl, apxs, httpd-std.conf, etc... we'll
>> have to come up with a couple sets of variables that parallel their $prefix
>> counterpars. For example:
> To further facilitate this, I suggest that apxs and apachectl should have a
> -d argument added to them, analogous to httpd's -d; otherwise they have no
> concept of what the ServerRoot is if httpd has been run with -d.



View raw message