It seems odd that closed source software could use GMP under the LGPLv3, but that a GPLv2 project could not. How tightly integrated is the GMP stuff? Aren't we pretty much just using it as a library?
--Mike On 9/23/07, David Joyner <[EMAIL PROTECTED]> wrote: > > On 9/23/07, William Stein <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > Michael Abshoff pointed out to me that GMP 4.2.2 has been released! > > Very exciting. The > > release notes list exactly one new feature: > > > > From http://gmplib.org/gmp4.2.html > > > > New features of GMP 4.2.2 > > * License is now LGPL version 3. > > Bugs: > > ... > > > > The obvious question is whether the _current_ version of Sage can > > include or even > > link to GMP 4.2.2 or any future version of GMP. The answer is *NO*. For > > more, > > see below. > > > > The Sage project as an overall project is -- and must be -- released > > under GPL v2 only, > > at least right now. I don't know when or if this will change. It is > > not within my power. > > Only time will tell. > > > > > http://gplv3.fsf.org/dd3-faq > > > which has a nice matrix showing what is legal to combine. > > > > This table very clearly says that a GPL v2 project cannot link in an > > LGPL v3 library. > > We will thus not be upgrading the Sage GMP package to 4.2.2 right now. > > > > Thoughts? > > The obvious suggestion is to ask them to license under > "LGPLv2 or greater". It can't hurt to ask. > > > > > William > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
