Re: [GSoC update] git-remote-svn: Week 11

From: Will Palmer <wmpalmer@gmail.com>
Date: Jul 12, 2010, 15:39 UTC
Message-ID: <1278949191.1611.5.camel@wpalmer.simply-domain>
In-Reply-To: <20100712152403.GH1931@jack.stsp.name>

On Mon, 2010-07-12 at 17:24 +0200, Stefan Sperling wrote:

Show 22 quoted lines

> On Mon, Jul 12, 2010 at 04:48:40PM +0200, Michael J Gruber wrote:
> > Ramkumar Ramachandra venit, vidit, dixit 12.07.2010 16:35:
> > > it will be pretty painful for Git developers to compile the SVN trunk
> > 
> > While this is certainly true for the "compilation" part, at least
> > getting the source is a snap for us:
> > 
> > git://git.apache.org/subversion.git
> > git://github.com/apache/subversion.git
> 
> Regarding compilation, take a look at tools/dev/unix-build/Makefile.svn
> in the Subversion tree. Possibly the most painful thing for git devs is
> that you'll need an svn binary somewhere in PATH, but any version will do.
> Then create an empty directory (say, ~/svn), copy the Makefile in there,
> and run make (requires GNU make). That will download and compile Subversion
> from trunk, including various dependencies.
> If all goes well, binaries (with debug symbols) end up in ~/svn/prefix/
> 
> On Linux, -devel packages for a couple of libaries may be needed
> (most likely openssl, zlib, expat, libproxy).
> 
> Stefan

This is all moot, because the whole point is that svndumpr compiles against libsvn, so you don't need the whole svn source-tree. All you need to get svndumpr working are some header files and a working libsvn. Everyone who currently uses git-svn already has a working libsvn, since perl's svn bindings wrap around libsvn anyway.