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

Re: Why do we allowed mixed versions of libsvn_* ?

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-12-04 16:15:53 CET

On Sat, 2004-12-04 at 09:44, Branko Čibej wrote:
> As long as we state that plainly in our compatibility guarantees; i.e.,
> that different rules apply for client-to-lib compatibility than
> lib-to-lib.

The issue is not client-to-lib versus lib-to-lib. A third-party library
accessing Subversion needs to be able to take advantage of our
compatibility rules, while our own client does not. The issue is
whether it's allowed to mix versions of Subversion components.

> Of course, basically we cheat if we change our compatibility
> rules between minor releases. :-)

I disagree that we have ever promised that we allow mixing of Subversion
component versions. We've certainly made it break, by using internal
function names between components. Practically, this has only caused a
problem when people upgraded all of Subversion without upgrading
mod_dav_svn.so, which is generally an accident resulting from binary
packages not taking care of the module upgrade.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 4 16:17:06 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.