On Nov 26, 4:43 am, "David Joyner" <[EMAIL PROTECTED]> wrote:
> I know of no code which in Sage which is GPLv2 only. William or Michael,
> please
> correct me if I am wrong.
Yes, as I mentioned above there is none.
> I think that code which is GPLv2 (only) is not GPLv2+ compatible,
> since GPL2+ says the
> modifications can be released under either GPL2 or GPL3 (at your choice).
> "GPLv2 only" restricts that choice.
Yes, and as is the standard Sage library cannot be GPL V2 only since
we have Apache 2 licensed code in the tree. We have that code as BSD
licensed code, so one can replace that, GSL and GNUTLS and
dependencies by GPL V2 licensed releases and the end result will be a
GPL V2 only Sage.
In general this discussion depends on how one interprets "combined
work" since with Python we use dlopn(), i.e. we don't link by some
people's definition. IANAL and it is irrelevant to the discussion
here, so I will stop.
In the very end we decided that the Sage library code needs to be GPL
V2+ compatible and it would take a major act to change this. It will
also have to pass the JSage panel (in case the vote would be say GPL
V2 only) and I don't see that happening.
re GPL V3: I am personally no fan of either the FSF or the GPL V3, but
I certainly like the GPL V2. But other people around here like the GPL
V3, but in the end we decided on GPL V2+.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
