On Sunday, June 24, 2001, at 03:33 PM, Graham Leggett wrote:
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.
It's not my intent for this to be the final packaging and distribution plan. It's really intended to get a rollup mechanism working, so we can talk turkey about where things really go from here.
My thinking is that simply making the proxy available for testing on the official httpd site will get more eyes on this code as we move towards release. Even little audience is more than we see now on dev.apache.org or via CVS.
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.
While users get everything in a rollup build (as they do now in 1.3, for the most part) there's no reason they have to run everything. They just load what they want in their config.
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.
That's why I'm proposing this first concrete step, so we can either start moving along to a resolution of this issue or decide this is the wrong way and abandon it.
Regards, Chuck
