Chuck Murcko wrote: > I'd like to try to fold mod_proxy into the next httpd-2.0 beta release. > We'll cut our own source tree (using the process we've discussed on > new-httpd). > > I'd also like to start putting source distribs of both 1.3 and 2.0 > mod_proxy out in a way similar to the 4/day CVS snapshots of httpd. > > I'd package them as release, except leave the CVS and .[a-z]* files in > the source tree. > > Make sense? > > Suggested place is http://httpd.apache.org/dist/mod_proxy/<release>/ > > I'd suggest packaging both the httpd tarball and a mod_proxy tarball. > > Thoughts?
The trouble is that this release will have little or no audience - a
user out there who knows nothing about mod_proxy and how it is packaged
will see apache_2.x.x.tar.gz and will download that - without mod_proxy.
This is a real problem - at the moment the entire proxy subproject has
essentially been orphaned. People are not going to download random
permutations of apache tarballs in the hope of getting the "right"
combination of modules. They must either get all or nothing.
Every time this subject is raised there is fierce discussion, but no
conclusion. I am not sure what the way forward is at this stage.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
