Why doesn't apache use a dependencies based make system
similar to the ports tree in FreeBSD?
This could be an extensible build system that would allow the
administrator to specify what modules you want, it could connect, sync
cvs/download tarball, configure, build, munge configuration files, and
install.
As things stand there isn't an _easy_ "build and extend
apache" system other than apxs, which I know is intimidating to some
admins. With the talk of mod_proxy and mod_rewrite becoming
submodules with different release cycles (which, IMHO, would be a
great idea), having such a build system would be pretty nice,
especially if the admin wants to get a newer version of the module.
-sc
PS I'm not talking about using a directory tree structure as
the ports does, I'm just referencing it as a system that automatically
fetches dependencies, builds, and integrates the software: in this
case with FreeBSD.
On Wed, Apr 18, 2001 at 08:41:39PM +0200, Graham Leggett wrote:
> Delivered-To: [EMAIL PROTECTED]
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Precedence: bulk
> Reply-To: [EMAIL PROTECTED]
> list-help: <mailto:[EMAIL PROTECTED]>
> list-unsubscribe: <mailto:[EMAIL PROTECTED]>
> list-post: <mailto:[EMAIL PROTECTED]>
> Delivered-To: mailing list [EMAIL PROTECTED]
> Date: Wed, 18 Apr 2001 20:41:39 +0200
> From: Graham Leggett <[EMAIL PROTECTED]>
> X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.17-0.6.1 ppc)
> X-Accept-Language: en
> To: [EMAIL PROTECTED]
> Subject: Re: [VOTE] mod_proxy in?
> X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N
>
> Jim Jagielski wrote:
>
> > 1. I forget... is mod_proxy it's own project (ala apr?) If not,
> > it should be.
>
> Keep one thing in mind though - splitting out modules into more and more
> sub projects means more and more work for the end user, both for
> compiling the server, and for installing it.
>
> Regards,
> Graham
> --
> -----------------------------------------
> [EMAIL PROTECTED] "There's a moon
> over Bourbon Street
> tonight..."
--
Sean Chittenden
PGP signature
