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 the associated recipe (.bb file) unless otherwise stated. License information for any other files is either explicitly stated or defaults to GPL version 2." Here "metadata" stands for "oe-core recipe", right ? What if we extend (*.bbappend) a GPLv2 recipe: is it "contaminated" or not ? Regards, contrib 2016-10-13 12:37 GMT+02:00 Burton, Ross <ross.bur...@intel.com>: > > 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 > file. > > Ross >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
