https://wiki.spdx.org/index.php?action=history&feed=atom&title=Talk%3ATechnical_Team%2FUse_Cases%2F2.0%2FBuild_System_Yocto 2026-05-07T15:34:09Z Revision history for this page on the wiki MediaWiki 1.23.13 https://wiki.spdx.org/index.php?title=Talk:Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=2361&oldid=prev 2013-04-10T15:26:53Z

<p>Import comments from Drupal site</p> <p><b>New page</b></p><div>== Minor points here ==<br /> <br /> A few comments:<br /> <br /> : 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> : http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html<br /> <br /> I'd use http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-... as it has the most up to date info.<br /> <br /> Elizabeth Flanagan<br /> Yocto Project<br /> elizabeth.flanagan@intel.com<br /> <br /> -- Submitted by Anonymous on Fri, 2012-05-25 03:30.<br /> <br /> == Yocto Project not just Yocto please ==<br /> <br /> The correct title for Yocto is &quot;the Yocto Project&quot;<br /> <br /> -- Submitted by Anonymous on Thu, 2012-05-24 04:44.</div>

MartinMichlmayr