Daniel Shahaf <d.s_at_daniel.shahaf.name> writes:
> Philip Martin wrote on Tue, Mar 26, 2013 at 10:09:21 +0000:
>>
>> Getting another package is probably an easier solution, however...
>>
>> The Subversion libraries are binary compatible so the binary from the
>> standard Ubuntu package should work with the libraries from the Eclipse
>> package. Extract the binary and put it somewhere on your PATH. Ubuntu
>> changes the so-version of the libsvn libraries, if the Eclipse package
>> doesn't do the same you would need to create some library symlinks as
>> well.
>
> IIUC, you are simply saying that instead of installing the 'subversion'
> package (which provides /usr/bin/svnversion), extracting the
> 'svnversion' binary from that package and adding it to $PATH should
> work.
>
> I agree, but I'm not sure how that simplifies things: the 'subversion'
> package contains little more than the binaries to begin with, so you
> won't save much by installing just parts of it.
The problem, as I understand it, is that the new package doesn't contain
an svnversion binary.
> The interesting part is that you might be able to use the 'svn' binary
> from the *old* system, too. (ie, old binary and new libraries) This
> should work for every other client, but the cmdline client sometimes
> uses subversion/include/private/ functions --- which breaks this
> use-case (practically at the runtime linker, though that's not
> guaranteed).
That's what I am suggesting. Extract the svnversion binary from the old
package that does provide it and use that binary with the new packages
that don't provide it.
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Received on 2013-03-26 13:48:20 CET