You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by cm...@collab.net on 2001/07/16 20:49:17 UTC
cvs2svn. And so it begins...
Well, it looks like I'll be diving into the cvs2svn repository
converter right about...now. Current plans are to gank CVS's
RCS-interfacing code and go at this entirely in C, resulting in a
GPL'ed converter. Other ideas that have been tossed around include a
using a Perl or Python RCS-parsing module.
Anyone who can spare the time to assist with this is welcome to join
in on the fun. Else, please continue devoting your attention and
patches to Subversion itself as it draws nigh unto an alpha release --
Ben and Karl will be grateful! :-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn. And so it begins...
Posted by John P Cavanaugh <ca...@soco.agilent.com>.
On Mon, Jul 16, 2001 at 03:49:17PM -0500, cmpilato@collab.net wrote:
> Well, it looks like I'll be diving into the cvs2svn repository
> converter right about...now. Current plans are to gank CVS's
> RCS-interfacing code and go at this entirely in C, resulting in a
> GPL'ed converter. Other ideas that have been tossed around include a
> using a Perl or Python RCS-parsing module.
Are you going to write the whole thing in C, or just use a C library
for parsing the RCS files??
I ask because doing the whole thing in C might make it more difficult
to leverage and create a vss2svn or clearcase2svn.
--John Cavanaugh
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn. And so it begins...
Posted by Karl Fogel <kf...@collab.net>.
Just FYI, folks:
We've re-prioritized a bit, and so Mike is putting off the cvs2svn
work in order to get the svn code to M3 readiness. We simply realized
that, with Subversion this close, him suddenly leaving it and pouring
his energies into cvs2svn would be a huge momentum sink, not just for
him, but for others who are accustomed to his responsiveness about
Subversion issues. (Not to mention the tandem coding he does with Ben
and me a lot.)
-K
"Justus Pendleton" <su...@ryoohki.net> writes:
> cmpilato@collab.net writes: > Other ideas that have been tossed around
> include a
> > using a Perl or Python RCS-parsing module.
>
> You may want to look into vcp, which gets mentioned on the perforce
> user's mailing list every now and again. I haven't used it myself
> but: "vcp (and the Perl module VCP.pm) is a system for copying
> resources under version control from one repository to another,
> possibly different, repository, or to/from RevML. Directory trees may
> be re-rooted, and only particular changes need be copied (or all can
> be copied)." Right now I believe it supports CVS and perforce. If it
> can already suck in a CVS repository then you've already got half the
> work done for you :-)
>
> The module is on CPAN so you can just do $ perl -MCPAN -eshell
> cpan> install VCP Justus
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: cvs2svn. And so it begins...
Posted by Justus Pendleton <su...@ryoohki.net>.
cmpilato@collab.net writes:
> Other ideas that have been tossed around include a
> using a Perl or Python RCS-parsing module.
You may want to look into vcp, which gets mentioned on the perforce user's
mailing list every now and again. I haven't used it myself but: "vcp (and
the Perl module VCP.pm) is a system for copying resources under version
control from one repository to another, possibly different, repository, or
to/from RevML. Directory trees may be re-rooted, and only particular
changes need be copied (or all can be copied)."
Right now I believe it supports CVS and perforce. If it can already suck in
a CVS repository then you've already got half the work done for you :-)
The module is on CPAN so you can just do
$ perl -MCPAN -eshell
cpan> install VCP
Justus
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org