From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] requiring Perl SVN libraries for git-svn
Date: 13 Dec 2006 13:17:05 -0800 [thread overview]
Message-ID: <86slfj1ooe.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20061213202142.GE8179@localdomain>
>>>>> "Eric" == Eric Wong <normalperson@yhbt.net> writes:
Eric> The API of the SVN:: libraries seem to be relatively stable these days
Eric> and are *much* faster than the command-line client. I plan on
Eric> maintaining compatibility with version 1.1 of the SVN libraries for at
Eric> least another year; or more if it's not a big problem.
For a while, I would have been upset. I was building SVN from fink, even
though I was using a private Perl as /usr/local/bin/perl. And since the Perl
bindings have to be built when the SVN package is built, it was being built
against the core Perl, which I didn't use, so I couldn't use the SVN bindings.
Now, I'm building SVN from darwinports, which builds its own Perl, and I have
~/bin/git-svn wrap the /opt/git/bin/git-svn passing it the /opt/local/bin/perl
instead of the first Perl in the path. And it all just works. I suppose
I could have done that before too. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
next prev parent reply other threads:[~2006-12-13 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 20:21 [RFC] requiring Perl SVN libraries for git-svn Eric Wong
2006-12-13 21:17 ` Randal L. Schwartz [this message]
2006-12-15 16:02 ` Seth Falcon
2006-12-15 18:44 ` Eric Wong
2006-12-15 21:06 ` Seth Falcon
2006-12-16 7:58 ` [RFC/PATCH 1/2] git-svn: remove support for the svn command-line client Eric Wong
2006-12-16 7:58 ` [RFC/PATCH 2/2] git-svn: rename 'commit' command to 'set-tree' Eric Wong
2006-12-16 13:26 ` Junio C Hamano
2006-12-16 21:44 ` Eric Wong
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=86slfj1ooe.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.