On 10 nov, 10:32, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > I'm not totally convinced though that it's okay to use GPLv3+ spkgs in > Sage (the question boils down to: is cvxopt part of Sage or does Sage > simply call cvxopt as external program). > > Jeroen.
Imagine the Sage library depended on GPLv3 code. Then by the GPLv3 license, we are forced to distribute Sage under a GPLv3. But that is done already. Sage is now distributed under GPLv2, so it is distributed under a GPLv3 too. Once this is agreed, nothing prevents you from distributing your own code under other licenses. As long as you make it clear that *only* the core Sage library is GPLv2, but not all components, I don't see you're getting into any trouble. However, if some contributor would license a patch as gplv3, that would be a horse of a different color: only the Sage library without the patch could be released under GPLv2, and it would be cumbersome to keep track of that. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
