Bug#721598: ITP: python-vcs -- Various version control systems management abstraction layer
On Mon, Sep 09, 2013 at 03:04:38PM +0200, Mike Gabriel wrote:
> Hi Jelmer,
>
> On Mo 09 Sep 2013 14:56:12 CEST Jelmer Vernooij wrote:
>
> >On Mon, Sep 09, 2013 at 01:35:06PM +0200, Mike Gabriel wrote:
> >>Hi Jelmer,
> >>
> >>On Mo 02 Sep 2013 21:08:50 CEST Jelmer Vernooij wrote:
> >>
> >>>On Mon, Sep 02, 2013 at 10:36:49AM +0200, Mike Gabriel wrote:
> >>>>Package: wnpp
> >>>>Severity: wishlist
> >>>>Owner: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
> >>>>
> >>>>* Package name : python-vcs
> >>>> Version : 0.4.0
> >>>> Upstream Author : Marcin Ku??mi??ski
> >>>><https://github.com/codeinn/vcs/issues>
> >>>>* URL : https://github.com/codeinn/vcs/
> >>>>* License : Expat
> >>>> Programming Lang: Python
> >>>> Description : Various version control systems management
> >>>>abstraction layer
> >>>>
> >>>> Python vcs is an abstraction layer on top of various
> >>>>(Mercurial, Git, as extra
> >>>> backends: SVN, Bazaar) version control systems. It is designed as a
> >>>> feature-rich Python library with a clear API Reference.
> >>>> .
> >>>> Features
> >>>> - Common API for SCM backends
> >>>> - Fetching repositories data lazily
> >>>> - Simple caching mechanism so we don???t hit repo too often
> >>>> - In-memory commits API
> >>>> - Command-line interface
> >>>> .
> >>>> Incoming
> >>>> - Full working directories support
> >>>> - Extra backends: Subversion, Bazaar
> >>>Where are the extra backends? I don't see them in the linked
> >>>upstream source code.
> >>
> >>I cannot tell you where the backends yet are. Currently, I am
> >>struggling with a licensing issue in vcs that you may be able to
> >>solve.
> >>
> >>For further info on this see this issue report on github:
> >>https://github.com/codeinn/vcs/issues/118
> >
> >It looks like Marcin already followed up to this. Dulwich and that file are
> >GPLv2 or later.
>
> I just dropped another comment on #118. As dulwich is GPL-2+ I
> pointed out the using dulwich in vcs requires vcs getting relicensed
> to a license that is GPL-2+ compatible.
Please note that that is true for not just Dulwich but also for
Mercurial (which is GPLed too).
Wouldn't it be fine for python-vcs to technically be MIT-licensed? I suspect it
would only become problematic if something that was not GPL-compatible wanted
to depend on python-vcs (and thus Dulwich/Mercurial).
Cheers,
Jelmer
Reply to: