* Andre McCurdy <armccu...@gmail.com> [150708 01:57]: > There are two separate issues.
> Both GPLv3 and LGPLv3 block 'Tivoization', which rules out [L]GPLv3 > for anyone needing to create signed firmware images which can not be > modified by the end user. > http://www.gnu.org/licenses/rms-why-gplv3.en.html > Quite separate from that, linking an application with a GPL library > (any version of the GPL) requires that the application be released > under a GPL or GPL compatible license, so GPL libraries are generally > considered to be incompatible with closed source applications. > (Dynamically linking with an LGPL library is generally OK since the > LGPL license doesn't transfer to the application). > http://www.gnu.org/licenses/gpl-faq.en.html#IfLibraryIsGPL > http://www.gnu.org/licenses/gpl-faq.en.html#GPLStaticVsDynamic > So for someone with a proprietary application which links dynamically > with nettle in a distro which can't use [L]GPLv3, the older version of > nettle with an LGPLv2 license would be the only option. Yep, that sounds correct to me and the sane thing for us to do. Cheers, Anders -- Anders Darander ChargeStorm AB / eStorm AB -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core