|[eigen] Eigen 3.1.1 and LGPL components|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: [eigen] Eigen 3.1.1 and LGPL components
- From: Clifford Yapp <cliffyapp@xxxxxxxxx>
- Date: Tue, 28 Aug 2012 11:56:54 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=YYsUe48lDWD/FQF5rHiB7FIwiZ33yMhYBDW5jm7wnqY=; b=J4skH4PE7evpOGwG5Kbz2rLC1GZlXoBkNUusxWOzLghZSJ0xuYcyVgkjfNcp0jwfsM sSG2byyLdQQUbJdIn5JOiSMmuKV0fmt1ArrhYbfaklsf8YOn8ogBAx99UTwKZsfoiFfa sXIHprcvqy+ehGlce5xU4YAs+IsasWK+7KffM61GTPTTvIHk89XBeuNfu2SR+fB3vs8A hWUq6+7fMQphPNcQdySFA2eMMTEwEABED2Wm+D1Up4PZ+yqnzgVd+trKWKha+9nEKzLS Dp9uHOux1fv3vnu4x7ShiyJerAxH10Zj7NfWS1bmZmX1DZnyucpRtnzDI3T/CBCtCcik qsVg==
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...