|Re: [eigen] Eigen 3.1.1 and LGPL components|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx, Clifford Yapp <cliffyapp@xxxxxxxxx>
- Subject: Re: [eigen] Eigen 3.1.1 and LGPL components
- From: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Date: Mon, 10 Sep 2012 13:31:21 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=qnDVqLE+2tM9lRsiE3PXw21lm8s4pEV4TlmMvWt9jG8=; b=F7FVjv/mupIThMzPM5+HdNL0n5Fczy47qGZ/OT64VxQdWaj5HOSKnSpvmp9aNfA9NU 0cDesIS9XsxcUgGz+SEnYEun5U7emkS9whMwRZAx307xsXHPD1EwdZu9ZNCKFYjuzeWn pDg9VCZ9vzGvr6Z5Q2uvmLTnqaYfYl2t53eOTOpFjzocQlE3H/K/uHRpeTXzGxU81dRK Mq4S2U98YIqhoUVY8HrOZ/iv9B/Qz5at4EAfvpFd98y2683jC6YIdL/3eVVO00GZlGlf Q4RfNYNeIabkHslX+YECSPO3WJMY12pH2Y/4uQOAOdCRoIQgDUcMrNLE1ObbIvN9NB+M 01mw==
This is finally fixed: 405ece2a6429 for the default branch, and
11b65f0601c4 for the 3.1 branch.
Indeed, I have checked that all the LGPL files, as found by
find . -type f | grep -v \\.hg | xargs grep 'GNU Lesser' | cut -d ':' -f 1
are using either LGPL 2.1 only (so the current LGPL3 text did not even
cover them!) or LGPL 2.1-or-later.
2012/8/28 Benoit Jacob <jacob.benoit.1@xxxxxxxxx>:
> Thanks for the heads up.
> Any remaining LGPL code in the Eigen tree is third-party code whose
> licensing is not decided by us.
> So the presence of the LGPL3 text only in the top-level directory is
> only a remnant from the pre-MPL2 days, as you guessed.
> This will be corrected shortly by adding a copy of the LGPL 2.1.
> 2012/8/28 Clifford Yapp <cliffyapp@xxxxxxxxx>:
>> I had a question about the LGPL components of Eigen 3.1.1 -
>> Looking at the remaining LGPL code in Eigen, it all appears to use the
>> LGPL 2.1 or later version of the LGPL. Yet, the toplevel copy of the
>> LGPL (well, OK, GPL + LGPL, thanks to that dual-file approach to the
>> new version) is LGPL v3.
>> For my purposes, the LGPLv2+ is a workable license, but the LGPLv3 is
>> not (long story...) - is the intent of the Eigen licensing to
>> constrain users of the LGPL components of Eigen to the LGPLv3 or
>> newer? Or (now that the MPL2 relicensing is complete and the
>> remaining LGPL code is LGPLv2+) would it be acceptable to regard the
>> LGPL components of Eigen as being distributed as LGPLv2+?
>> I'm really hoping that the LGPLv3 license files in the toplevel are a
>> holdover from pre-MPL2 days and LGPLv2+ will be workable, since there
>> don't seem to be any LGPLv3 specific constraints other than the
>> decision of the Eigen developers themselves...