Hi,
thank you for your quick and helpful response.
Just for clarification:
I am working on a GPL 2 licensed software and may not modify the licence,
yet we are not using any further GPL or secondary licensed software. Does
that mean I am contravening against 3.3 in particular:
" The Larger Work must be "a combination of Covered Software with a work
governed by one or more Secondary Licenses." So you can't just say "I really
prefer (L)GPL" - you must have a need to combine with another, existing GPL
work. (This is different from a traditional dual-license, which does not
require you to combine, and instead allows you to simply say "I've decided
to be GPL-only.")"
Thank you for your help
Mark
Am 30.06.2013 04:25, schrieb Gael Guennebaud:
There is practical guide there:
http://www.mozilla.org/MPL/2.0/combining-mpl-and-gpl.html
Since you're not going to modify Eigen's source code, you have nothing
special to do!
cheers,
gael
On Sat, Jun 29, 2013 at 10:37 AM, Mark <mark.ortmann85@xxxxxxxxx> wrote:
Hi everybody,
I have already read the thread "MPL2 is really compatible with GPL/LGPL",
yet I am still unsure about how to proceed.
I want to use Eigen (and only Eigen) within a GPL 2 licensed software, which
has been available for a long time and we cannot change the license (or
"extend" it).
According to http://www.mozilla.org/MPL/2.0/FAQ.html Q14 requirement 1 is
met by Eigen. However, we are not yet using any other GPL licensed third
party library, therefore I am not sure if we fulfill requirement 2.
My questions are:
1. Can I combine Eigen within my GPL 2 software?
2. Do I have to change/modify my license?
3. How do I meet requirement 3 of Q 14 (MPL/FAQ)?
4. Do I have to add a license file (as in Eigen COPYING.*)?
Please note I am not intending to modify any of the Eigen source code and
would really love to use this library within my software.
Thanks for your help,
Mark