Talk:Technical Team/Use Cases/2.0/Build System Yocto

Minor points here

A few comments:

This needs verification but the license field is generally high leveland may not break down the complete licensing for a package. As an example, a package could be listed as GPL v2 which would be in the License field but the package may contain BSD, MIT, etc sub elements.

So, from a recipe perspective, each build artifact that is to be packaged should have it's license included in the LICENSE field of the recipe.

If a recipe contains multiple packages and those packages have different licenses, then we can specify the package's contained licenses via LICENSE_{$PN}. I'm sure there are cases where we don't do this but should.

http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html

I'd use http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-... as it has the most up to date info.

Elizabeth Flanagan Yocto Project elizabeth.flanagan@intel.com

-- Submitted by Anonymous on Fri, 2012-05-25 03:30.

Yocto Project not just Yocto please

The correct title for Yocto is "the Yocto Project"

-- Submitted by Anonymous on Thu, 2012-05-24 04:44.