Open tjohns opened 10 years ago
Dulwich being GPL doesn't mean pyvcs needs to be GPL licensed as well, just that it needs to have a license that is compatible (which the BSD license is).
Note that bzrlib and hg are both also GPL.
@jelmer :
Dulwich being GPL doesn't mean pyvcs needs to be GPL licensed as well, just that it needs to have a license that is compatible (which the BSD license is).
Wouldn't linking / importing GPL code trigger a derivative? Doesn't that mean pyvcs is now GPL?
On Sat, Nov 08, 2014 at 11:13:19AM -0800, Tony Narlock wrote:
@jelmer :
Dulwich being GPL doesn't mean pyvcs needs to be GPL licensed as well, just that it needs to have a license that is compatible (which the BSD license is).
Wouldn't linking / importing GPL code trigger a derivative? Doesn't that mean pyvcs is now GPL? Sortof.
It doesn't make the pyvcs GPL per se, but in practice you can only use it under the GPL (or a license compatible with the GPL).
(IANAL)
Cheers,
Jelmer
FWIW Dulwich has been relicensed to dual Apache version 2.0 / GNU GPL v2 or later. This should make its license compatible with pyvcs.
I hate to bring this up, but I noticed you're linking against Dulwich, which is licensed under GPLv2+. This would mean that pyvcs would need to be licensed under GPL as well.
Which is unfortunate, because I'd prefer a more liberal license myself. The Dulwich maintainer is trying to get that project re-licensed under Apache 2, though it looks like he hasn't heard back from everyone necessary to do that yet.
Just thought I'd mention it, since license compliance is important.