Description of problem: Macaulay2 is GPLv2. It is linked with mpfr, which is "LGPLv3+ and GPLv3+ and GFDL". Macaulay2 might also be responsible for holding back updates to mpir due to license incompatibility; see bug 680892. Is upstream considering GPLv2+ at all? If not, is compiling without mpfr/mpir an option? Version-Release number of selected component (if applicable): Macaulay2-1.4-4.fc18.x86_64 How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Upstream finally replied to my query, ------------------ I am just now looking into this again -- thank you for the prompt. I have just checked in a change to the trunk expanding the statement in M2/INSTALL to say the our source code is licensed under GPL 2 or 3 and restricting the statement in the variable "copyright" accessible from the running M2 program to say that the binary code is licensed under GPL 3. That should take care of it. ------------------ which should resolve things
* Wed May 30 2012 Rex Dieter <rdieter> - 1.4-5 - License: GPLv2 or GPLv3 (#821036) Turns out we'll likely end up linking against gmp moving forward anyway, for increased compatibility with Singular (stay tuned).