I have now added the missing lgpl-v3.txt to the mpir-1.2.2 tarball.
Moreover, I have checked carefully every other "past" tarball in the
MPIR web facing directory (whether linked from the site explicitly or
not) to ensure that they already contained both the GPL v3 *and* LGPL
v3 texts. Thankfully
The Free Software Foundation have just been of great assistance in
sorting this issue out.
In an email to us, they have pointed out a very embarrassing omission.
In fact the MPIR 1.2.2 tarball is missing the LGPL v3 license text.
The GPL v3 text is there, but not the LGPL v3 text. Fortunately it i
On 4 May 2010 20:26, Antony Vennard wrote:
> Well... you know what I mean. Let me put it another way:
>
> the issue was corrected and current distributions and licenses are all
> correct.
>
> Or:
>
> I cannot see any evidence of mpir distributed tarballs licensed as
> lgplv2+ containing lgplv3+ co
Well... you know what I mean. Let me put it another way:
the issue was corrected and current distributions and licenses are all
correct.
Or:
I cannot see any evidence of mpir distributed tarballs licensed as
lgplv2+ containing lgplv3+ code.
Antony
On 05/04/2010 08:22 PM, Bill Hart wrote:
> "No
"Now rectified"? The tarballs have not changed since Oct/Nov last year!
But yeah, otherwise it is a fair assessment.
On 4 May 2010 20:12, Antony Vennard wrote:
> Ok thanks, sorry, I wasn't certain the issues were tarball-only so I
> looked in svn.
>
> I have looked at the tarballs also and can c
Ok thanks, sorry, I wasn't certain the issues were tarball-only so I
looked in svn.
I have looked at the tarballs also and can confirm the same findings as
Bill. Certainly, it seems the code being distributed is being done so in
the correct manner.
This would seem to show that the issue is now re
Thanks. The issues you raise:
1) The mpir-parallel svn branch contains LGPL v3+ code. However, this
was branched from MPIR 2.0.0, which is already LGPL v3+, so this is
absolutely fine.
2) Brian Gladman's version of mpf/set_str.c contains some code the
same as the version in GMP 5. This is because
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 ear
I apologise in advance for the length of this email.
Ok, I've checked out the entire svn.
grep -ir "lgplv3" * gives:
branches/mpir-parallel/mpn/x86_64/.svn/text-base/mulmid_basecase.asm.svn-base:dnl
LGPLv3+, license terms reproduced below. These modifications are hereby
branches/mpir-parallel/m
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 an
10 matches
Mail list logo
