[oe] [PATCHv2] recipe licenses: update recipe LICENSE fields
fransmeulenbroeks at gmail.com
Thu Oct 21 08:39:30 CEST 2010
2010/10/20 Denys Dmytriyenko <denis at denix.org>:
> GPLv2 and GPLv3 are not compatible. Thus, there cannot be a derivative work
> that combines those two. But if one piece of code is GPLv2+ and another is
> GPLv3, the resulting combination is licensed under GPLv3.
> So, it's always good to know which libraries you have as strict GPLv2 and
> which are "GPLv2 or later", even in case when you are Ok with GPLv3, you
> should know to not use strict GPLv2 code in any GPLv3 projects...
Note that this applies to programs. A derivative work that just
combines things is quite possible afaik (e.g. a linux kernel (v2 only)
and a recent samba (v3))
Whether using a v2 only and v3only shared lib in an app is possible is
unsure to me; static linking with v2 and v3 is afaik a no-no.
More information about the Openembedded-devel