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

Re: Avoiding multiple library copies on a system

From: Branko Čibej <brane_at_wandisco.com>
Date: Fri, 13 Jul 2012 10:34:59 +0100

On 12.07.2012 21:20, Peter Samuelson wrote:
> Reposting under a new thread + subject line, at Daniel's suggestion.
> [Markus Schaber]
>> So my personal experience tells me that multiple-client scenarios are
>> the common case, and that the deployment strategy (only using linux
>> distro packages, or 3-in-1 bundles like VisualSVN) can reduce that
>> problem.
> So, we provide a pile of libraries that maintain ABI backward
> compatibility. You can have as many different svn client apps on a
> given system as you want, and so long as they are all using the same
> copy of our libraries, there is no cross-version compatibility problem.

Like I said in my response to this in the other thread -- API or even
ABI compatibility is not the issue. Working copy formats, wire protocol
quirks, etc. etc. are more "interesting". And I really don't think it's
up to us to tell packagers how to do their stuff.

-- Brane

Certified & Supported Apache Subversion Downloads:
Received on 2012-07-13 11:35:38 CEST

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.