On Wed, Sep 19, 2001 at 01:05:27AM +0200, Graham Leggett wrote:
> Greg Stein wrote:
>
> > I'm +1 on creating httpd-rollup, and -0.5 on putting proxy back in.
>
> Ok - first question - what do we call the rollup release:
>
> o Option A: apache-2.x.x.tar.gz
>
> Combines httpd-2.0, apr, apr-util, httpd-proxy and
> httpd-ldap and produces an apache rollup tree.
>
> o Option B: apache-2.x.x.tar.gz, apache-modules-2.x.x.tar.gz
>
> Combine httpd-2.0, apr, apr-util into apache-2.x.x.tar.gz,
> and combine httpd-proxy, httpd-ldap into apache-modules-2.x.x.tar.gz.
>
> o Option C: apache-2.x.x.tar.gz, apache-proxy-2.x.x.tar.gz,
> apache-ldap-2.x.x.tar.gz
>
> Combine httpd-2.0, apr, apr-util into apache-2.x.x.tar.gz,
> and combine httpd-proxy into apache-proxy-2.x.x.tar.gz, and
> combine httpd-ldap into apache-ldap-2.x.x.tar.gz.
>
> o Option D: something else...
+1 on Option A. I think that anything else is going to be too
confusing for end users.
Considering that we do not have a way to build static modules
outside of the tree without rerunning buildconf, I really
dislike having separate tarballs (Options B or C).
The CVS repositories are distinct, but a release by the
Apache Group combines all of the subprojects that we deem
worthy/stable for inclusion.
My $.02. -- justin
