|Re: [eigen] Eigen 3.1.1 and LGPL components|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Eigen 3.1.1 and LGPL components
- From: Clifford Yapp <cliffyapp@xxxxxxxxx>
- Date: Wed, 29 Aug 2012 09:27:29 -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=hMAmL2F0zY06DYh38sLs+5YaWEpVZDoYinUeh/VPqUQ=; b=zILBV727EsaIvYUXqExKxF+72VamVuKbgP3MIvInR0zJB4hEom/Xr7Z9SKRTN5Kgy/ 1twr41La08C8kwpZc+2jOZrbFCqAFcY9bGnjsl2nsmSpJ7jBFstP2DT3ugyMHepKj9e1 C/ogYITzpx0Q7JthJXGl24vE7CIu1W4JUh2bzKdwTeF8MpkjcxO+gSTRLyQS66HIWa2o pQSsJdlHCqRo3rVD4prsHnNsMvh+s+D/R6Wtt0U6oNzI2gVilEDkwZBB6okKyBLzFj+c 98mxg2Br/DzFZ2MFXLBO5aZT1ttOc+ri7E9NNMIr0wmpsCKaKmb34Ddq2GEpcjVSjGxW OoUg==
On Wed, Aug 29, 2012 at 3:16 AM, Gael Guennebaud
> it's "LGPL2.1, or (at your option) any later version". So, it's LGPL3 too.
I suppose you could add both license versions, but usually in my
experience folks just include the LGPL2.1 - since the code has the "or
any later version" clause, projects wanting to restrict subsequent
work to only higher versions of the LGPL can substitute the newer text
themselves (although usually it's a better idea to keep the original
license + "or later versions" clause when possible, in my experience -
going "newer only" on LGPL/GPL projects where the original baselines
on the older version essentially guarantees a fork.) The implication
of including the newer license text is usually "there is some part of
this work that isn't OK under just LGPL2.1 or later, so we need to
include LGPLv3". If you do opt to include both license texts, I'd
suggest an explicit note in the COPYING.README file clarifying that
there isn't any LGPLv3 only code in Eigen.
Cheers, and thanks again for taking the time to clarify this!