Re: Question about cvs2svn and CVSNT

jason kendall wrote:
> I noticed on the FAQ page for cvs2svn
> (http://cvs2svn.tigris.org/faq.html#cvsnt) that converting CVSNT
> repositories to svn using cvs2svn may be problematic and is not supported.
> 
> Does anyone know if any patches of cvs2svn are planned that might
> address this?

It would be great to support CVSNT conversions better, to help CVSNT
users get out of their quasi-proprietary world and onto a modern VCS.
But I know of no current work in this direction.  I think that CVSNT
support is waiting for volunteers or sponsor$.  Maybe you would like to
play one of those roles?

A big chunk of the work of adding robust CVSNT support is to figure out
exactly how CVSNT repositories differ from standard CVS repositories.
That will take some work poring through CVSNT documentation,
repositories, and perhaps even source code.  We already know about some
of the differences but probably not all of them.

Then a bit of work would have to be done on the RCS parser that is used
by cvs2svn to retain "newphrases" that are used by CVSNT but which the
parser currently discards.  The main point here is to handle the "kopt"
value, which specifies, revision by revision, what expansion options to
use for the file contents (text vs. binary, keyword expansion, etc).
(Standard CVS only allows such options filewise.)

It might also be nice to handle the commitids that are used by CVSNT and
by newer versions of CVS, though I consider this support to be optional
because our changeset detection is already pretty reliable.

Let me know if you would like to tackle any of these tasks and I will
give you some tips to help get you started.

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2618199

To unsubscribe from this discussion, e-mail: [[email protected]].