NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Bah (Score:1)
Just for the sake of saying so, It is possible to browse using file, svn, AND http in http://search.cpan.org/~claco/Catalyst-Model-SVN-0.05/ [cpan.org]
That's what powers http://handelframework.com/source/ [handelframework.com]
It wasn't fun, and it wasn't pretty, but it does work. My biggest beef is the fetching content/logs on a tab/branch url. I can't just ask for it by url, since it's a copy; you have to stroll through the logs till copy event, and then get the original from its original location at the time of the copy.
Makes some sense, but it's certinaly not a way to do the API in a usable manner.
Reply to This
Re: (Score:1)
Do you see much use of the http:/// [http] access? I've done some benchmarking comparing SVN::Repos (file:/// only) with SVN::Ra (file:/// and svn://). Carrying out 11 runs each of SVN::Web's test suite, SVN::Ra takes about 15% longer to run the tests than SVN::Repos.
Re: (Score:1)
The SVN Perl bindings are not so readable. Trolling through C source docs/doxygen (when it works) isn't my idea of usable pod w/ examples.
I was under the impression that Ra, or at least it's perl bindings couldn't do all forms of connections (svn, file, http). I'm sure htt
Re: (Score:1)
That has recently (like, last week) improved, as a big commit was made to Subversion to expand on the Perl documentation and provide more examples.
But yes, I've often had to fallback to writing a short hack to exercise a particular API function and use Data::Dumper on the result to divine what's being returned.