httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: cvs commit: apache-1.3/src CHANGES
Date Mon, 09 Nov 1998 21:41:15 GMT
Martin Kraemer wrote:
> 
> On Mon, Nov 09, 1998 at 03:03:49PM -0500, Jim Jagielski wrote:
> > Rodent of Unusual Size wrote:
> > > APACI [...] appears to have exceeded its
> > > charter -- to the extent that configuration fixes (like
> > > this suExec thing and mod_perl) are being made to work
> > > with APACI at the expense of working with src/Configure.
> >
> > This was my main concern.
> 
> 
> !? Again: what has APACI / configure to do with the "well known" way
> (i.e., manually editing suexec.h)? If you ignore configure, you won't
> be bothered by its functionality (It will never interfere with your
> src/Configuration file).  But IF YOU USE IT, you will be
> rewarded by an astonishingly easy way to configure your whole server
> environment in a (albeit complicated long) single line. That's a
> killer criterion for all those vendors out there who want to repeatedly
> and reproducably generate the same (in different version numbers)
> binary Apache package.
> 

yeah... like it would be with a single Configuration file that does
the exact same :)

Again, the idea behind APACI, and on which it was approved IIRC, was that
it provide a Front-end to Configure, not that it do things that Configure
can't, nor that it's "default" results differ from those of a default
Configure. It was supposed to compliment, not exclude or force.

-- 
===========================================================================
   Jim Jagielski   |||   jim@jaguNET.com   |||   http://www.jaguNET.com/
            "That's no ordinary rabbit... that's the most foul,
            cruel and bad-tempered rodent you ever laid eyes on"

Mime
View raw message