Philip Martin wrote on Tue, Mar 26, 2013 at 10:09:21 +0000:
> Daniel Shahaf <d.s_at_daniel.shahaf.name> writes:
>
> > Arno Steffens wrote on Mon, Mar 25, 2013 at 23:04:22 +0100:
> >
> >> I use SVN inside eclipse, but this seems not to provide the
> >> "svnversion" functionality I need to make sure that my compiled code
> >> is identically to the checked in (with or without added M to
> >> version)
>
> Use "svn status" instead?
>
> >> Unfortunatly the svnpackage for my old Ubuntu isn't compatible to the
> >> newer required 1.7SVN with comes with eclipse. So I can't use this
> >> .
> >>
> >> Can someone give me a hint? Thanks!
> >>
> >
> > As already suggested: you might consider looking for other packages (or
> > backports) before compiling it yourself.
>
> 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 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).
Received on 2013-03-26 12:17:00 CET