Re: cvs2svn (was: Re: Initial version of svntest regression test framework is ready.)

Greg Stein wrote:

> I intend to work on cvs2svn at some point. Looking over what kbob did, I
> think that we may need to start again.

I agree.

The current version:

        uses way too much memory.

        goes compute bound for several minutes sorting the
        commits on small repositories.

        Doesn't really parse RCS files right -- the CPAN module
        I used is a hacky parser.

        Can't directly call the repository access layer, since
        it's not in C.

        No way to implement deltas without reimplementing
        the vdelta code.

At the time I stopped working on it, I couldn't get any traction into
the editor interface, since that was right about when the editor
interface was changing hourly, and the XML stuff wasn't ready
either (nobody could read it).

Another thing to think about: How will cvs2svn tell the repository,
"This commit isn't happening now, it happened two years ago in
March"? And what are the security implications of that?

So what's an acceptable amount of time to convert a 9 Gb repository?
One week? One day?

> Oh, and knowing about RCS parsing is a "kind of"
> requirement (there are both Perl and Python modules to do this, so the bar
> is lowered for the parsing part).

Don't use the Perl parser. Do read rcsfile(5).

-- 
Bob Miller                              K<bob>
kbobsoft software consulting
http://kbobsoft.com                     kbob_at_jogger-egg.com