Greg Stein wrote:
> Ah. I think I understand where you're going. There are two RMs:
>
> 1) the httpd RM (releasing the bare bones httpd)
> 2) the "rollup" RM (releasing httpd + many modules)
>
> At the moment, RM2 only yanks in mod_proxy.
Almost - but there should only ever be one release of Apache, ever. (For
the benefit of the end user who does not want to be confused).
There should be two RM's:
1) The proxy|rewrite|ssl RM (releases a stable mod_whatever to a known
location)
2) The "rollup" RM (releasing httpd + many modules)
RM1's job is to publish a stable mod_whatever to a known location. This
does not have to happen every single time there is an Apache release,
only if there are changes to a stable tree.
RM2's job is to roll Apache + APR + APR-utils + modules. RM2 uses a
standard script to get things done. The testing phase after the roll
will determine any problems, including whether a module is having
integration problems, and these should be fixed as they normally are.
What I'm saying we should do here is exactly what we are doing already
with APR and APR-util. They are in separate CVS trees, they get pulled
and intergated at release time, the release model works. All we need do
is add mod_proxy, mod_rewrite, etc and we are laughing.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
