|[eigen] Relicensing Eigen|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
- Subject: [eigen] Relicensing Eigen
- From: Keir Mierle <mierle@xxxxxxxxx>
- Date: Thu, 28 Jun 2012 11:45:30 -0700
- 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=O+c0eD17ruSZsxkuCFLYHTH7TlXQNMAU9Ayzq0nsy3Y=; b=G50OupxYULMt4u5GFw8PH6lbn2LSxRxtbDisDENxAbjYiaLAGG64sqmfFxQ5rsrPl+ BFSekLs7flv8t5FKqTR7i0yy05AJGaeL8BgTDVnEdU0Rc5rJ9xsfXYmNrFfKtGjiuV3a Zjh/SS9u4YG+lnaYH26GNGj1PthTpu5X4P9ReOUXeyBp0LEG5X02J2Vy5qGVFiFkScwd MQ56gKUENhl/Uj7hP5cuyGnAZqYFjc/NZvj12tjc/DsIv7LuB3yRQbNoIEuwdaoYKV3V i9MwRDRfkTUD/oQ9PE2zmmEF3FFZExctPuzldu2F/kd8M4KH8gJVOSMcbT7CHyqiCqXT R6MA==
Has there been any progress on moving to MPL 2.0 (or, even better, BSD/MIT)? I am now in the difficult position of not being able to use Eigen, or even my own contributions to Eigen, due to the license. LGPL3 compliance is not as trivial as the Eigen webpage suggests, according to an OSS-knowledgeable lawyer I have talked to about Eigen. Removing an Eigen dependency from my code is not trivial.
If the relicense can't happen, and on a reasonably short timeframe (a month or two) I may have to consider starting an API compatible re-implementation of the subset of Eigen we need. Obviously, this is the last thing I want to do.