A fabulous idea, IMHO.  

Basically, as Chuck stated that you suggested, a PORTS system for
Apache.

Have there be dist files for each of the external modules, for a given
httpd release, which are maintained in CVS with respect to the latest
stable version of each external module.  So that, the admin says:
./configure --enable-proxy, but proxy really isn't included - it's
just a dist file. configure then fetches the corresponding tagged
release listed in the dist file from cvs (or, from a set of releases
at apache.org via FTP/HTTP/CVSup/what-have-you), and builds
it. Special options for any module would have to be maintained in the
dist file as well - a little hairy, but not bad.

That would be the way to go, for me.

Victor 
-- 
Victor J. Orlikowski
======================
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

Reply via email to