incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: Including snapshot dependencies from other ASF projects
Date Fri, 17 Nov 2006 23:03:37 GMT
Garrett Rooney wrote:
> On 11/17/06, William A. Rowe, Jr. <> wrote:
>> John O'Hara wrote:
>> > I don't think its the same as releasing another projects code.
>> > A good example is when SubVersion included APR as part of its code
>> > base.  No one would have confused that as a release of APR, and
>> > it was patched and modded, and the APR team were kept in the loop.
>> Actually, in spite of a wide open-door policy from the apr team to the
>> svn and httpd developer communities, it indicates a breakdown of apr
>> meeting the needs of svn (it's second consumer) and in svn failing to
>> effectively participate in apr.  So I actually find it a bad example :)
> That's total BS.  The svn and httpd teams worked quite hard to get
> their fixes in to APR, and I'm not aware of them either distributing
> patched releases, only snapshots, and eventually releases.  The only
> reason that releases and snapshots were distributed was that for a
> long time you couldn't expect to find APR installed on most machines,
> and the svn team wanted to avoid requiring people to scramble around
> looking for dependencies.  

Yes - the failures were early on and remedied (and amusingly enough, the
situation around expat and pcre in httpd has similarly improved.)  I was
speaking of the early failures that we learned from.

> These days it isn't even distributed as
> part of the default release tarball, but as part of a separate deps
> tarball that just holds extra dependencies.

Yup - living on the bleeding edge of a support library is an interesting
place to be.  The point was not to slam svn about apr, or httpd about pcre
or expat, but to point out that this is a problem to be solved.  It's not
(living with snapshots of dependent sources) an issue that we should worry
about persisting.  And in this case it *is* part of the release the project
is voting on, and in one sense, becomes a release of the dependency.

Paul explained it clearly.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message