VCP for Foo <-> subversion conversion?

Hi. I'm the developer of VCP, a repository -> repository copying tool
that (currently) works with VCS, p4, and (beta) VSS:

    http://public.perforce.com/public/revml/index.html

You can also get the source from CPAN:

    http://theoryx5.uwinnipeg.ca/CPAN/data/VCP/VCP.html

Is there any interest in writing to/from subversion backends? I can
help out if somebody wants to do the bulk of the work (I'm fresh out of
tuits--working on branching), and there are already VCP::Source::CVS and
VCP::Dest::CVS, etc, to start with, so a VCP::Source::svn and a
VCP::Dest::svn should not be too hard to get to. I am really glad to
read about the goal of increased scriptability of subversion...

The idea is for VCP to be a tool that acts as a hub between many
disparate systems using two live connections (one to the source, one to
the dest) for online copying or a RevML file for offline copying.

Right now, it does change set aggregation (even when copying to cvs,
though cvs loses this info), though it does not handle
branching. I'm working on branching and establishing a branch map as we
speak.

All access is currently through command line invocations for the sake of
generality and portability (no need to distribute binaries to folks not
compiler-enabled), but we are planning on building high speed
direct-to-backend modules.

FWIW, VCP so far has been funded by Perforce thus far and Perforce is
quite interested in seeing VCP and RevML used as a standard tool for
interchange between repositories.

Thanks,

Barrie

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 29 18:01:30 2002