Agreed. I'd like to pop APR 0.9.1 out the door (or see somebody do it), then replicate the various logic bits over to apr-util and release that.
Once done, then we can "detach" httpd from the floating APR(UTIL) stuff. Specifically, since httpd uses the FIND_APR m4 macro, it can find a pre-installed APR rather than always using the bundled one. The hardest problem is that httpd uses m4 files from APR. That means that APR *must* be present at srclib/apr/ when somebody runs 'buildconf'. After that, we *might* be able to toss srclib/apr, but I doubt it. I bet there are still quite a few paths into srclib/apr/build/ for Apache's build system. (but then again, I haven't looked... maybe when the FIND_APR work was done, everything was switched over to use the "found" APR rather than assuming that APR was placed into srclib) Regardless... from a *tagging* standpoint, we should stop tagging APR(UTIL) with httpd tags. When we bundle releases, it should be done using three tags: one for httpd, one for apr, and one for apr-util. Cheers, -g On Sun, Sep 08, 2002 at 11:49:06PM -0400, [EMAIL PROTECTED] wrote: > > +1, as soon as both APR and APR-util have a release. > > Ryan > > On Sun, 8 Sep 2002, Ian Holsman wrote: > > > APR now has version management. > > is it time to stop just tagging the HEAD of the apr/apr-util trees > > when we make a release and just use the offically released ones? > > ie.. we would bundle apr 0.9.1 with httpd 2.0.41, > > and possibly further on, not bundle apr in the httpd-tar ball, and > > just document/check the minimum version required? > > > > --Ian > > > > -- > > _______________________________________________________________________________ > Ryan Bloom [EMAIL PROTECTED] > 550 Jean St > Oakland CA 94610 > ------------------------------------------------------------------------------- -- Greg Stein, http://www.lyra.org/
