|Re: [eigen] Important: Relicensing Eigen to MPL2|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Important: Relicensing Eigen to MPL2
- From: Gael Guennebaud <gael.guennebaud@xxxxxxxxx>
- Date: Sat, 21 Jan 2012 22:58:07 +0100
- 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 :content-type; bh=V048S2rXFSlB/x8R4hxPo6duOZ6SYn5f2LEcf2y3Z2o=; b=X6d+pefLaXOIEM29QtAvqlfcpmQa0SZhY3xup1FHSACW0lB8nUTltlZgJ/IjrIVKvz kBZCaVKuCOaYzBjHzI+k2rEj8LeyNlaVp/79nDSWD0PzYyVTr6VpPn2fDqAPsRzwEWfZ 8/KaYxo+fLQZUDK3fInOHb4AsspIiS1Bbl2b8=
On Sat, Jan 21, 2012 at 4:20 PM, Benoit Jacob <jacob.benoit.1@xxxxxxxxx> wrote:
> 2012/1/21 Rohit Garg <rpg.314@xxxxxxxxx>:
>> I am not in favor of BSD/MIT/Apache etc.
>> My criteria are
>> a) Does MPL2 require redistribution of changes to Eigen itself?
> Yes, but specifically only for the files that come from the
> MPL2-licensed software. That's called file-level copyleft. So if you
> make an improvement to Eigen's own files, and distribute software
> based on that improved Eigen, you have to allow people to get these
> Eigen improvements. If on the other hand you improve Eigen from the
> outside (e.g. you add a new feature without modifying existing files)
> then there is no copyleft requirement. In the case of Eigen, that
> doesn't make much of a difference since my understanding of the LGPL3
> Section 3 is that things were already working that way. But at least
> it's much more explicit with MPL2, without room for corner cases.
I'd just like to emphasize that Eigen is not all about headers, we
also have blas and lapack interface libraries, and for them the MPL2
is a clear bonus where people won't have to bother wrt dynamic vs
Since it is file based, the MPL2 also clarifies the situation with our
plugin mechanism, for which it is still not clear to me whether the
LGPL3.0 is OK with our wills on this subject.