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 Yocto recipe is GPL2, and we extend (*.bbappend) this recipe,
> does contamination effect applies to the extented recipe ?

The oe-core metadata is licensed under MIT, as explained in the LICENSE

yocto mailing list

Reply via email to