{"thread":{"id":"43430","subject":"[RFC] requiring Perl SVN libraries for git-svn","startedAt":"2006-12-13T20:21:42Z","lastAt":"2006-12-15T16:02:38Z","messageCount":3,"participants":["Eric Wong","Seth Falcon","Randal L. Schwartz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"294748","messageId":"20061213202142.GE8179@localdomain","threadId":"43430","inReplyTo":null,"subject":"[RFC] requiring Perl SVN libraries for git-svn","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2006-12-13T20:21:42Z","receivedAt":"2006-12-13T20:21:42Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Are there any git-svn users out there who would be seriously hurt if I\ndropped support for using the svn command-line client in git-svn?\n\nThe API of the SVN:: libraries seem to be relatively stable these days\nand are *much* faster than the command-line client.  I plan on\nmaintaining compatibility with version 1.1 of the SVN libraries for at\nleast another year; or more if it's not a big problem.\n\nLately, I've introduced support for authentication and connecting to\nrepositories with limited read permissions, as well as reading from the\nconfig files in ~/.subversion; so everything that could be done with\nthe command-line client backend can be done with the libraries, too.\n\n-- \n"},{"id":"295110","messageId":"86slfj1ooe.fsf@blue.stonehenge.com","threadId":"43430","inReplyTo":"20061213202142.GE8179@localdomain","subject":"Re: [RFC] requiring Perl SVN libraries for git-svn","fromName":"Randal L. Schwartz","fromEmail":"merlyn@stonehenge.com","sentAt":"2006-12-13T21:17:05Z","receivedAt":"2006-12-13T21:17:05Z","isPatch":false,"sender":{"key":"merlyn@stonehenge.com","avatar":"https://gravatar.com/avatar/dc528d210743ff0333e6213f9ee7b33b23f1b7bc1f3c5a8c2d819074ecd7ab19?d=mp&s=160"},"body":">>>>> \"Eric\" == Eric Wong <normalperson@yhbt.net> writes:\n\nEric> The API of the SVN:: libraries seem to be relatively stable these days\nEric> and are *much* faster than the command-line client.  I plan on\nEric> maintaining compatibility with version 1.1 of the SVN libraries for at\nEric> least another year; or more if it's not a big problem.\n\nFor a while, I would have been upset.  I was building SVN from fink, even\nthough I was using a private Perl as /usr/local/bin/perl.  And since the Perl\nbindings have to be built when the SVN package is built, it was being built\nagainst the core Perl, which I didn't use, so I couldn't use the SVN bindings.\n\nNow, I'm building SVN from darwinports, which builds its own Perl, and I have\n~/bin/git-svn wrap the /opt/git/bin/git-svn passing it the /opt/local/bin/perl\ninstead of the first Perl in the path.  And it all just works.  I suppose\nI could have done that before too. :)\n\n-- \nRandal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095\n<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>\nPerl/Unix/security consulting, Technical writing, Comedy, etc. etc.\n"},{"id":"294807","messageId":"m2vekddu5d.fsf@ziti.local","threadId":"43430","inReplyTo":"20061213202142.GE8179@localdomain","subject":"Re: [RFC] requiring Perl SVN libraries for git-svn","fromName":"Seth Falcon","fromEmail":"sethfalcon@gmail.com","sentAt":"2006-12-15T16:02:38Z","receivedAt":"2006-12-15T16:02:38Z","isPatch":false,"sender":{"key":"sethfalcon@gmail.com","avatar":"https://gravatar.com/avatar/fd62fe73d3013b12fce71d5269ec52eaca3c4cee479efc6eea3603d6f1d8bf8d?d=mp&s=160"},"body":"Eric Wong <normalperson@yhbt.net> writes:\n> Are there any git-svn users out there who would be seriously hurt if I\n> dropped support for using the svn command-line client in git-svn?\n>\n> The API of the SVN:: libraries seem to be relatively stable these days\n> and are *much* faster than the command-line client.  I plan on\n> maintaining compatibility with version 1.1 of the SVN libraries for at\n> least another year; or more if it's not a big problem.\n\nI've been using the SVN:: libraries and agree that that they work well\n(and faster).  One downside I see is that the svn command-line stuff\nwill Just Work for a lot of folks, whereas obtaining or building svn's\nPerl bindings can be more of a chore [*1*].\n\nOTOH, using git-svn via the svn CLI is slow and much less fun than\nwith SVN::.  So I can also see an additional argument to drop so that\npeople's first impression of git-svn won't be, \"gaah, slow\" -- because\nwith the SVN:: libs, my experience has been, \"yaah, much faster!\" :-)\n\nMy $0.02.\n\n+ seth\n\n\n[*1*] I asked our sysadmin to install the Perl libraries on one of our\nnew servers and although they seem to be installed, they are\nnon-functional.  git-svn stiffles the error messages, but a simple\nscript that just tries to require SVN::Core gives:\n\n    Can't load\n    '/usr/lib/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/SVN/_Core/_Core.so'\n    for module SVN::_Core:\n    /usr/local/src/subversion-1.4.2/subversion/libsvn_ra_dav/.libs/libsvn_ra_dav-1.so.0:\n    undefined symbol: PKCS12_SAFEBAG_free at\n    /usr/lib/perl5/5.8.8/x86_64-linux-thread-multi/DynaLoader.pm line 230.\n\nAnyone else seen this?  I guess that if you drop the svn command-line\nsupport, that it would then make sense to error out with more complete\n"}]}