On 2010-11-10 10:13, Minh Nguyen wrote: > It depends on whether your're talking about the Sage library (i.e. the > package sage-x.y.z.spkg) or some other spkg. Components of Sage > (spkg's) are covered by GPL compatible licenses. As far as I know, > there is no single license that covers the whole of Sage. Anything > that goes into Sage must be licensed under a GPL compatible license. > For example, the Sage library is covered by GPLv2+ and the policy (as > I understand it) is to include only code licensed under GPLv2+. We > don't include code under the GPLv3+ in the Sage library. Apart from > the Sage library, spkg's must be licensed under a GPL compatible > license. This means it can be licensed under the GPLv3+, which is the > case with the standard spkg GLPK.
First of all, thanks for the clear answer. I was actually talking about spkgs, more precisely cvxopt (#6456). The new version of that spkg is GPLv3+. 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. -- 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
