Hello,
it seems that license.manifest file describes application/lib/etc.
source code license,
but what about Yocto recipe license itself ?
So what is the license of a Yocto recipe ?
How to know it ?
If a Yocto recipe is GPL2, and we extend (*.bbappend) this recipe,
does contamination effect appli
On 14 October 2016 at 06:23, Contrib Open Source <
contrib.open.sou...@gmail.com> wrote:
> Here "metadata" stands for "oe-core recipe", right ?
>
"metadata" includes all the recipes and classes in oe-core.
> What if we extend (*.bbappend) a GPLv2 recipe: is it "contaminated" or not
> ?
>
Presu
Hello,
thanks for pointing me to oe-core LICENSE file.
Just to be sure, from:
https://github.com/openembedded/openembedded-core/blob/master/LICENSE
"All metadata is MIT licensed unless otherwise stated. Source code
included in tree for individual recipes is under the LICENSE stated in
On 13 October 2016 at 09:49, Contrib Open Source <
contrib.open.sou...@gmail.com> wrote:
> it seems that license.manifest file describes application/lib/etc.
> source code license,
> but what about Yocto recipe license itself ?
> So what is the license of a Yocto recipe ?
> How to know it ?
> If a
Hello,
it seems that license.manifest file describes application/lib/etc.
source code license,
but what about Yocto recipe license itself ?
So what is the license of a Yocto recipe ?
How to know it ?
If a Yocto recipe is GPL2, and we extend (*.bbappend) this recipe,
does contamination effect appli
