You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Doug MacEachern <do...@pobox.com> on 1998/12/11 21:34:36 UTC

--layout

Why doesn't this new option have a default?  I also had to 'touch
Configuration.apaci'.  These both break automated build scripts that people
have written for 1.3.x, including mod_perl's Makefile.PL, can this breakage
not happen please?

-Doug

Re: --layout

Posted by Doug MacEachern <do...@pobox.com>.
At 09:17 PM 12/11/98 -0500, Rodent of Unusual Size wrote:
>Doug MacEachern wrote:
>> 
>> Why doesn't this new option have a default?
>
>As discussed, there is no default in order to obey the Principle
>of Least Astonishment.  

Funny, I am Most Astonished by these configuration changes! ;-(

-Doug

Re: --layout

Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Doug MacEachern wrote:
> 
> Why doesn't this new option have a default?

As discussed, there is no default in order to obey the Principle
of Least Astonishment.  The majority of people commenting on
the issue wanted the 'default' behaviour to be Apache Classic
paths.  Since APACI has been out there for a while, though, changing
the default to this would have been a Bad Thing.  So neither
is the default as a compromise: don't change the default layout
for the existing APACI users (i.e., from GNU-like to Apache Classic),
nor for those moving from src/Configure to ./configure (i.e.,
from Apache Classic to GNU-like).  Both now have to make an explicit
choice.

At least that's my take on this.
-- 
#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://WWW.Dummies.Com/