| Re: [eigen] Re: Important: Relicensing Eigen to MPL2 |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Re: Important: Relicensing Eigen to MPL2
- From: Gael Guennebaud <gael.guennebaud@xxxxxxxxx>
- Date: Sat, 21 Jan 2012 22:49:53 +0100
- Cc: Benoit Jacob <jacob.benoit.1@xxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=M0V1RQE0YV/eK8bZwxWxtZrFYSqEIWTnMsIwU1Q1qPE=; b=IH0Lmi+JS/iiW5sVqEBXo4YetiwMD7ITooNBAh/D1jxv9oD6va4ntFfUXsfgmN7cYg N/keL15z4RMS47fCH7FmYvZcwcRZ0N+NjJj0RJE7uygCfwgyWs+0zUUOQxhxoD1JuRtk Ws976KZYur818z3ydNe7BVTbINN6Vm+lrfmms=
On Sat, Jan 21, 2012 at 5:18 AM, Radu B. Rusu <rusu@xxxxxxxxxxxxxxxx> wrote:
> The last point is a bit worrisome. What would be a good mechanism to inform the user about which parts of Eigen should
> (s)he use and which not, if (s)he does have licensing constraints (i.e., cannot use GPL code)?
Well, in the case Eigen is used as a wrapper to another lib, then,
since Eigen is header only, the user explicitly has to link to this
external library, so he/she really cannot miss the fact he/she has to
satisfy to the license of the external lib. Of course, on our side we
should also emphasize as clearly as possible the respective license of
the supported library everywhere it makes sense in the doc.
I should also recall that currently there are some pieces of code that
we integrated from existing LGPL libs. It is very unlikely that we can
re-license such code. FYI, this concerns the AMD reordering algorithm
and the sparse simplicial cholesky solver. The good thing is that
currently they are into quite well isolated modules.
cheers,
gael