You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Arno Steffens <ep...@gmx.de> on 2013/03/25 23:04:22 UTC
compile just svnversion (in addition to the eclipse-plugin)
Compiling SVN is somewhat demanding for a beginner. Is there a shorter way to compile the tool "svnversion" with less dependencies and effort? Are really all the stuff SQLite ... is needed for this?
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)
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!
Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Arno Steffens,
am Montag, 25. März 2013 um 23:04 schrieben Sie:
> 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)
Maybe you could be more specific on the environment your are talking
about or what exactly are your trying to achieve and one can provide
alternatives. Normally after an update if there are no modifications
in your working copy the code has to be checked in.
> Can someone give me a hint? Thanks!
Did you already try pre compiled packages from WanDisco or Collabnet?
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Arno Steffens wrote on Tue, Mar 26, 2013 at 14:54:09 +0100:
> I finally extracted binary and some libs out of a newer Ubuntu version.
> Just 5 libs (sqlite, svn_delta, diff, subr, wc) hasn't been enough for this.
> A Linux guru super tip has been to just put this libs into some extra folder and
> call svnversion with a different LD_LIBRARY_PATH and copy just a shell script to
> the /usr/bin:
>
> #!/bin/sh
> export LD_LIBRARY_PATH=/home/user/svnfix/lib:$LD_LIBRARY_PATH
> /home/user/svnfix/svnversion $1 $2 $3 $4
>
No offence to your guru, but that's better written like this:
#!/bin/sh
LD_LIBRARY_PATH=/home/user/svnfix/lib:"$LD_LIBRARY_PATH" /home/user/svnfix/svnversion "$@"
... and unless it's a single-user system, it's a bad idea for /usr/bin
binaries to refer a /home/user this way.
Cheers
Daniel
> Thanks all of you helping me with your ideas!
> Arno
>
>
>
> Gesendet: Dienstag, 26. März 2013 um 13:47 Uhr
> Von: "Philip Martin" <ph...@wandisco.com>
> An: "Daniel Shahaf" <d....@daniel.shahaf.name>
> Cc: "Arno Steffens" <ep...@gmx.de>, users@subversion.apache.org
> Betreff: Re: compile just svnversion (in addition to the eclipse-plugin)
> Daniel Shahaf <d....@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
Aw: Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Arno Steffens <ep...@gmx.de>.
I finally extracted binary and some libs out of a newer Ubuntu version.
Just 5 libs (sqlite, svn_delta, diff, subr, wc) hasn't been enough for this.
A Linux guru super tip has been to just put this libs into some extra folder and
call svnversion with a different LD_LIBRARY_PATH and copy just a shell script to
the /usr/bin:
#!/bin/sh
export LD_LIBRARY_PATH=/home/user/svnfix/lib:$LD_LIBRARY_PATH
/home/user/svnfix/svnversion $1 $2 $3 $4
Thanks all of you helping me with your ideas!
Arno
Gesendet: Dienstag, 26. März 2013 um 13:47 Uhr
Von: "Philip Martin" <ph...@wandisco.com>
An: "Daniel Shahaf" <d....@daniel.shahaf.name>
Cc: "Arno Steffens" <ep...@gmx.de>, users@subversion.apache.org
Betreff: Re: compile just svnversion (in addition to the eclipse-plugin)
Daniel Shahaf <d....@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
Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Philip Martin <ph...@wandisco.com>.
Daniel Shahaf <d....@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
Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Philip Martin wrote on Tue, Mar 26, 2013 at 10:09:21 +0000:
> Daniel Shahaf <d....@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).
Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Philip Martin <ph...@wandisco.com>.
Daniel Shahaf <d....@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.
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: compile just svnversion (in addition to the eclipse-plugin)
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Arno Steffens wrote on Mon, Mar 25, 2013 at 23:04:22 +0100:
> Compiling SVN is somewhat demanding for a beginner. Is there a shorter
> way to compile the tool "svnversion" with less dependencies and
> effort? Are really all the stuff SQLite ... is needed for this?
>
SQLite, APR, APR-Util are required even for this use-case.
You can build with:
% make svnversion
But I'm not quite sure you how'd install. I'd start with
% make -n install | grep svnversion
> 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)
> 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.