[Mark Phippard]
> We talked about this last year and decided we were going to update to
> the latest APR. I do not see any reason to change that decision.
That is a fundamental policy change, then. In the past you have
committed to binary compatibility for the Subversion library API until
2.0. Now you are breaking it, at least for those who use the deps
tarball - which to me represents an official endorsement.
I'm also disappointed because last time a related issue came up - I
advocated allowing libsvn-with-apr-0.9 and libsvn-with-apr-1.x to be
installed in parallel (so apps would automatically use whichever one
they were compiled with) - my idea was shot down specifically because
it would not honor the promise of binary compatibility until 2.0. Now
your situation will be even worse: not only will libsvn be
binary-incompatible, but third-party apps will _need_ to be recompiled
or they will crash. Maybe I'm weird, but I'd much rather have an app
use an older version of libsvn (or complain at startup that you deleted
that older version) than try to use the latest libsvn and then
misbehave or crash randomly at runtime.
Justin in particular was pretty vocal in his belief that my proposal
would break promises to the users. I hope he opposes this change at
least as strenuously, for the same reason.
--
Peter Samuelson | org-tld!p12n!peter | http://p12n.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-08 16:29:05 CEST