[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    =?UTF-8?B?W0lzc3VlIDE3MThdIE5ldyAtIGN2czJzdm4ucHkgcHJvYmxlbWF0aQ==?=
From:       dionisos () tigris ! org
Date:       2004-01-26 18:55:54
Message-ID: 20040126185554.7876.qmail () tigris ! org
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=1718
                  Issue #:|1718
                  Summary:|cvs2svn.py problematic 'co' dependency
                Component:|subversion
                  Version:|current
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|NEW
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P3
             Subcomponent:|tools
              Assigned to:|issues@subversion
              Reported by:|dionisos






------- Additional comments from dionisos@tigris.org Mon Jan 26 10:55:54 -0800 2004 -------
In several issues it has been noticed that the 'co' dependency for cvs2svn.py is
making cvs2svn.py more strict than we want.

There are several reasons not to depend on rcs's co:

1) We can change rcsparse to accept files generated by CVS or CVSNT
2) We don't depend any obscure rcs bugs which might exist
3) Setting up and running co.exe on windows is a recurring item on the lists
because of failed attempts

Having said that, the solution to this problem is to build an all-python
solution on top of the rcsparse RCS parser. As a matter of fact, I started such
a project a few weeks ago.

Created this issue to track progress on the matter (after consulting cmpilato on
irc).

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org

[prev in list] [next in list] [prev in thread] [next in thread]