From: Stefan Sperling <stsp@elego.de>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: "Ramkumar Ramachandra" <artagnon@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Sverre Rabbelier" <srabbelier@gmail.com>,
"Greg Stein" <gstein@gmail.com>,
"Daniel Shahaf" <d.s@daniel.shahaf.name>,
"Will Palmer" <wmpalmer@gmail.com>,
"David Michael Barr" <david.barr@cordelta.com>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Bert Huijben" <rhuijben@collab.net>,
"Sam Vilain" <sam@vilain.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [GSoC update] git-remote-svn: Week 11
Date: Mon, 12 Jul 2010 17:24:03 +0200 [thread overview]
Message-ID: <20100712152403.GH1931@jack.stsp.name> (raw)
In-Reply-To: <4C3B2B48.4070408@drmicha.warpmail.net>
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
next prev parent reply other threads:[~2010-07-12 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 14:35 [GSoC update] git-remote-svn: Week 11 Ramkumar Ramachandra
2010-07-12 14:48 ` Michael J Gruber
2010-07-12 15:24 ` Stefan Sperling [this message]
2010-07-12 15:39 ` Will Palmer
2010-07-12 18:12 ` Ramkumar Ramachandra
2010-07-14 8:58 ` Stefan Sperling
2010-07-12 16:00 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100712152403.GH1931@jack.stsp.name \
--to=stsp@elego.de \
--cc=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=david.barr@cordelta.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gstein@gmail.com \
--cc=jrnieder@gmail.com \
--cc=rhuijben@collab.net \
--cc=sam@vilain.net \
--cc=srabbelier@gmail.com \
--cc=wmpalmer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).