Roger Keays writes:
> I liked the sound of svk
> (http://svk.elixus.org), except after reading the code and documentation I
> found it didn't seem to match up to svn's largely well documented, well
> commented C code. No offence intended to the author of course - I just get
> a little bit intimidated by long lists of perl code with no whitespace or
Sure, the code readability and the documentation definitely needs
improvement, and is constantly being improved. Please let me know if
you find specific code segments that makes you uncomfortable.
> What have people's experiences with svk been like?
svk has be used by people other than me. Most noticeably Best
Practical Solutions has been using it to maintain many branches of
their product "RT" for different customers. With the merge facility
they saved uncountable hours merging changes across branches.
Eric Wilhelm writes:
> Well, svk is only at revision 0.15, so you've got to allow some bloody edges,
> but what I would like to know (and it doesn't seem to be in the svk
> documentation) is why are there 4500+ code lines of perl needed to make
> subversion distributable? (the fact that there are more white lines than
> comments is also disturbing.)
*cough* It's now 0.16.
First of all, there are about 3200 Perl statements in svk. About 900
are to replace libsvn_wc, which has 11987 lines with comments
stripped. libsvn_client also has 10918 lines.
And there are code to support the merge history tracking.
And there are probably some magic code to make Perl faster than C
> The way I see it, this could be done (albeit in-efficiently) with the svn
> tool, some hook scripts, and a little glue. Here's a scenario:
Sure everyone could write such thing; I've said I'll be more than
happy if someone wants the reimplement the feature svk provides in svn
in C, since I won't have to maintain things and I could just ask
people to fix things. But until now there's no such someone doing
things I need. And code speaks louder.
Received on Mon Jul 5 20:31:59 2004
- application/pgp-signature attachment: stored