git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Stefan Sperling <stsp@elego.de>
Date
Jul 12, 2010, 15:24 UTC
Message-ID
<20100712152403.GH1931@jack.stsp.name>
In-Reply-To
<4C3B2B48.4070408@drmicha.warpmail.net>
On Mon, Jul 12, 2010 at 04:48:40PM +0200, Michael J Gruber wrote:
Show 8 quoted lines
> 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
Previous: Michael J GruberNext: Will Palmer
Message 3 of 7 in “[GSoC update] git-remote-svn: Week 11”
  1. Ramkumar RamachandraJul 12, 2010
  2. Michael J GruberJul 12, 2010
  3. Stefan SperlingJul 12, 2010
  4. Will PalmerJul 12, 2010
  5. Ramkumar RamachandraJul 12, 2010
  6. Stefan SperlingJul 14, 2010
  7. Michael J GruberJul 12, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.