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

From: Michael J Gruber <git@drmicha.warpmail.net>
Date: Jul 12, 2010, 16:00 UTC
Message-ID: <4C3B3C14.8040002@drmicha.warpmail.net>
In-Reply-To: <20100712152403.GH1931@jack.stsp.name>

Stefan Sperling venit, vidit, dixit 12.07.2010 17:24:

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

That Makefile pulls in (and compiles) a lot of stuff which may or may not be what you want.

In terms of Git development, I prefer a Git checkout (rather than a svn checkout) of the subversion code where I can bisect happily. Fulfilling most dependencies using devel packages was not a real problem (Fedora 13), just an iterative process...

The most painful part is that older svns (e.g. 1.4.6) don't seem to like newer autoconf (2.65) so that compatibility testing gets difficult, especially because (due to the branch structure of the code) merge bases of, say, 1.5.0 and trunk go quite a way back (1.5.0~955).

Michael