From: Seth Falcon <sethfalcon@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] requiring Perl SVN libraries for git-svn
Date: Fri, 15 Dec 2006 08:02:38 -0800 [thread overview]
Message-ID: <m2vekddu5d.fsf@ziti.local> (raw)
In-Reply-To: <20061213202142.GE8179@localdomain> (Eric Wong's message of "Wed, 13 Dec 2006 12:21:42 -0800")
Eric Wong <normalperson@yhbt.net> writes:
> Are there any git-svn users out there who would be seriously hurt if I
> dropped support for using the svn command-line client in git-svn?
>
> The API of the SVN:: libraries seem to be relatively stable these days
> and are *much* faster than the command-line client. I plan on
> maintaining compatibility with version 1.1 of the SVN libraries for at
> least another year; or more if it's not a big problem.
I've been using the SVN:: libraries and agree that that they work well
(and faster). One downside I see is that the svn command-line stuff
will Just Work for a lot of folks, whereas obtaining or building svn's
Perl bindings can be more of a chore [*1*].
OTOH, using git-svn via the svn CLI is slow and much less fun than
with SVN::. So I can also see an additional argument to drop so that
people's first impression of git-svn won't be, "gaah, slow" -- because
with the SVN:: libs, my experience has been, "yaah, much faster!" :-)
My $0.02.
+ seth
[*1*] I asked our sysadmin to install the Perl libraries on one of our
new servers and although they seem to be installed, they are
non-functional. git-svn stiffles the error messages, but a simple
script that just tries to require SVN::Core gives:
Can't load
'/usr/lib/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/SVN/_Core/_Core.so'
for module SVN::_Core:
/usr/local/src/subversion-1.4.2/subversion/libsvn_ra_dav/.libs/libsvn_ra_dav-1.so.0:
undefined symbol: PKCS12_SAFEBAG_free at
/usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/DynaLoader.pm line 230.
Anyone else seen this? I guess that if you drop the svn command-line
support, that it would then make sense to error out with more complete
next prev parent reply other threads:[~2006-12-15 16:02 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
2006-12-15 16:02 ` Seth Falcon [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vekddu5d.fsf@ziti.local \
--to=sethfalcon@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).