Re: Licensing issue with cvs2svn

Daniel Berlin <[email protected]> Tue, 22 Sep 2009 11:52:53 -0400
Newsgroups gmane.comp.version-control.subversion.cvs2svn.devel
Message-ID <[email protected]>
On Tue, Sep 22, 2009 at 10:21 AM, Michael Haggerty <[email protected]> wrote:
> Hello,
>
> I'm the main maintainer of cvs2svn, which is under a CollabNet license.
>
> Greg Ward has been working on cvs2hg, a variation of cvs2svn that
> converts directly to Mercurial.  For this work, he would like to "import
> mercurial" from cvs2svn code (it is Python) and push the output to
> Mercurial via its API.
>
> The problem is that Mercurial is GPLv2, and it is not clear to me that
> the CollabNet license is compatible with GPLv2; it seems likely that it
> is not.  Therefore it is at best questionable whether linking cvs2svn
> and Mercurial is permitted [1].

As long as mercurial is separately distributed from cvs2hg and it is
the user who is "linking", it doesn't really matter.

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

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