On Mon, 2 Dec 2002, Blair Zajac wrote:
> In looking at cvs2svn, it appears to only work on CVS repositories
> that you have a copy of.
>
> For projects that it's not easy to get hold of to CVS repository,
> it would be useful to have cvs2svn work on remote repositories
> (i.e. via :pserver:).
>
> How easy/hard would this be?
Impossible.
Well, I guess it's not technically impossible, but it would be slower than
molasses and hard on the server.
> Is cvs2svn set up to easily be
> expanded to handle it?
cvs2svn parses the RCS files that make up the repository, to gather the
information needed for branches, etc.
It then uses the RCS commands to get the various revisions it wants,
when it wants, from that RCS file.
The second part would be easy (but slow) to do remotely, and would be very
hard on the remote server (since it would be requesting every single
revision of every single file. It would also do it in the order that will
take the longest, since it will go earliest revisions first, which, for
CVS, is the worst case).
The first part you'll have to parse out of CVS's output, and to do
correctly, requires doing things like running "cvs status -v" on the
entire repo, and parsing out the tags that each file has.
Unfun in the extreme.
> > Best, > Blair
>
> ---------------------------------------------------------------------
> 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
Received on Mon Dec 2 22:39:06 2002