[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why svn 2.0 may come sooner than we expected

From: Ben Reser <ben_at_reser.org>
Date: 2004-07-02 01:14:40 CEST

On Thu, Jul 01, 2004 at 06:30:55PM -0400, Greg Hudson wrote:
> If I understand the outcome of
> http://marc.theaimsgroup.com/?l=apr-dev&m=108860637218865&w=2 right, apr
> 1.0 may not ship with an apr-config (it would ship with an apr-1-config
> instead), in which case we wouldn't be supporting apr 1.0 without a
> local hack. And I think that's well and proper; it would make life
> harder on third-party application developers to have two sets of
> incompatible Subversion ABIs running around.

Why? Most of them either are source based or build our libraries into
their application statically anyway. I still fail to see how it's
making life harder for them. They don't have to do anything spectacular
to support APR 1.0. Even if it ends up being apr-1-config we already
have --with-apr= where you can specify the full path. Fine so we don't
support APR 1.0 by default. Make people do:

If we were that worried about something like this we should:
a) Not have used APR types directly in any of our APIs.

b) Hidden any required use of APR from applications.

But that would mean wrapping gobs of APR functionality that I don't
think we want to do.

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 2 01:15:31 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.