httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Terbush <ra...@Covalent.NET>
Subject Re: [PATCH] APACI configure changes
Date Mon, 30 Nov 1998 15:31:32 GMT
Rodent of Unusual Size <Ken.Coar@Golux.Com> writes:
> Ralf S. Engelschall wrote:
> > 
> > Wait please, Randy. At least the special --GNU-paths I dislike very much,
> > sorry. I really want to see a --with-layout=ID where ID can be "apache",
> > "gnu", whatever.
> 
> It is very clear to me that the current default path layout
> is not on; sufficient people have voted for the equivalent of
> 'make --compat the default.'

The patch I submitted does revert to the /usr/local/apache with the
old conf/ bin/ logs/ layout. 

> Someone suggested removing the concept of a default layout,
> so configure would gritch unless either --compat or --GNU-paths
> (or the equivalents) were explicitly selected.  I like that
> idea; it obeys the PLA.

I think that I would personally like to see some base default that
just running 'configure' would use.

> I like the idea of having a single option to configure that
> provides the choice of path layouts.  I would in fact go
> one step further than Ralf, and suggest that maybe we
> could have something like '--layout=foo' in which 'foo'
> is the basename of a file containing the path layout
> info.  Then we could provide apache.layout and gnu.layout,
> and sites could define -- and use/maintain -- their own
> layouts using those as templates.  Have configure look
> at the layout file and gritch if there are any missing items.

I like this idea, but thought that it was a bit major for this late
stage. These cycles would be much better spent on 2.0. 

I do  like the idea of "vendor" layouts though. We could perhaps
default to a layout.`uname` if not specified then.

> I also like the idea of having src/Configure create the ../Makefile;
> this is more in line with the idea of configure being a wrapper.

I looked at doing this, but the changes are too major for this late
stage IMHO. That looks like a religious battle that I cannot see
resolving before the end of the year.

> Just off the top of my head.  I'm glad someone has taken this
> particular bull by the horns. :-)

There are a couple of other changes that I want to include that I did
not have in the patch.

1. Copy apachectl in place using the TARGET name as the prefix. 
   ie. httpdctl, httpd-fpctl, httpd-perlctl
2. Add --target flag to 'configure' to override any TARGET define
   within the rest of the build process.



Mime
View raw message