Let's just clarify this bit shall we, just in case: The below should read "mpir-trunk" uses a small number of lgplv3+ patches and is distributed as lgplv3+. By same license, I meant the same license as the relevant patches.
Just so we are clear. I do not wish to be mis-quoted. > mpir 1.3 and earlier contain only lgplv2+ code. mpir-trunk (to be > mpir-2.0) uses a small number of lgplv3+ patches and is distributed > under the same license. > > Antony > > On 05/04/2010 04:43 PM, MPIR Team wrote: >> Dear All, >> >> you may be aware of statements on the GMP website regarding MPIR. We >> have been passed email correspondence in which Torbjorn Granlund again >> alleges that we are distributing a: >> >> "renamed GMP package with license downgraded from LGPL 3 to LPGL 2.1" >> >> But we have no idea what he means. If anyone has any information about >> this, can you please post it here publicly to our list so we can >> resolve this situation as soon as possible! >> >> The allegations apparently relate to the MPIR website, but as far as >> we know, all tarballs there are correctly licensed and prominent notices are >> given as to their licensing status. >> >> We sincerely appreciate anyone who can shed light on this issue or assist >> us. >> >> Best Regards, >> >> The MPIR Team. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "mpir-devel" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/mpir-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
