https://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&feed=atom&action=historyTechnical Team/Use Cases/2.0/Build System Yocto - Revision history2024-03-29T01:11:56ZRevision history for this page on the wikiMediaWiki 1.23.13https://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=2510&oldid=prevBschineller at 18:18, 21 May 20132013-05-21T18:18:50Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 18:18, 21 May 2013</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>'''Title:''' Yocto Build System</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>'''Title:''' Yocto Build System</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">UPDATE 05/21/2013: Yocto project is actively trying to utilize SPDX.  Here's a writeup they did https://bugzilla.yoctoproject.org/show_bug.cgi?id=4516</ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>'''Background:'''</div></td><td class='diff-marker'> </td><td style="background-color: #f9f9f9; color: #333333; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #e6e6e6; vertical-align: top; white-space: pre-wrap;"><div>'''Background:'''</div></td></tr>
</table>Bschinellerhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1879&oldid=prevMartinMichlmayr: Convert to MediaWiki syntax2013-03-07T13:18:52Z<p>Convert to MediaWiki syntax</p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 13:18, 7 March 2013</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"><p><strong><br /></strong></p><p><strong></del>Title:<del class="diffchange diffchange-inline"></strong>&nbsp; </del>Yocto Build System<del class="diffchange diffchange-inline"></p><p><strong></del>Background:<del class="diffchange diffchange-inline"></strong>&nbsp;</p><p></del>Note: This is not a detailed background. You are encouraged<del class="diffchange diffchange-inline">&nbsp; </del>to read up on the Yocto Project by using the following link:<del class="diffchange diffchange-inline">&nbsp; <a href="</del>http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html<del class="diffchange diffchange-inline">">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p></del>The Yocto Project provides a build system which can be used to provide, as an example, a file system/kernel/boot loader image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).<del class="diffchange diffchange-inline"></p><p></del>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.<del class="diffchange diffchange-inline">&nbsp;</p><p><strong></del>Primary Actors:<del class="diffchange diffchange-inline"></strong></p><p></del>Yocto User: Receives a Yocto build for a device. Executes the build.<del class="diffchange diffchange-inline"></p><p></del>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.<del class="diffchange diffchange-inline"></p><p></del>the Yocto Project: Provides the Yocto build system.<del class="diffchange diffchange-inline"></p><p></del>Build System Provider: They provide a<del class="diffchange diffchange-inline">&nbsp; </del>Yocto based build, for example for their product. They may also provide patches to Packages that the recipes pull or may even add their own packages.<del class="diffchange diffchange-inline"></p><p><strong></del>Goal in Context:<del class="diffchange diffchange-inline"></strong>&nbsp; </del>To execute a Yocto based build and generate an image for a hardware device or simulator<del class="diffchange diffchange-inline">&nbsp; </del>and to have SPDX documents that describe the licensing for all copyrightable artifacts pulled in by the build system and used to generate that image (i.e. not just artifacts that make it into the image, everything and everything that it pulls including the build system). <del class="diffchange diffchange-inline">&nbsp;</del>Note: envision we could be talking about 1000's of related SPDX documents<del class="diffchange diffchange-inline"></p><p><strong></del>Stakeholders and Interests:<del class="diffchange diffchange-inline"></strong>&nbsp;</p><p></del>Yocto User:<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>A. To receive accurate and clear information of licensing for all copyrightable<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>elements used in the build and for the build system.<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>B. To be able to comply easily with licenses for all copyrightable elements used in<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;</del>the build and the build system.<del class="diffchange diffchange-inline"></p><p><br /> </del>2. Package Maintainer:<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>A. To communicate the license information for their package.<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>B. To have their licenses respected.<del class="diffchange diffchange-inline"></p><p>&nbsp;</p><p></del>3. the Yocto Project:<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>A. To communicate the license information for their build system and <del class="diffchange diffchange-inline"><span style="text-decoration: underline;"></del>the licensing of each package<del class="diffchange diffchange-inline"></span></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>(currently via the license field in a recipe).<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;</del>B. To have their licenses respected.<del class="diffchange diffchange-inline"></p><p>&nbsp;</p><p></del>4. Build System Provider:<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>A. To communicate the licensing information for the build they are providing.<del class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </del>B. To comply with all the licenses used in the build the system they are providing.<del class="diffchange diffchange-inline"></p><p>&nbsp;</p><p><strong></del>Preconditions:<del class="diffchange diffchange-inline"></strong></p><ol><li></del>A yocoto build is created.<del class="diffchange diffchange-inline"></li><li></del>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.<del class="diffchange diffchange-inline"></li><li></del>A patch for a package used in the build is created.<del class="diffchange diffchange-inline"></li></ol><p>&nbsp;</p><p><strong></del>Main Success Scenario:<del class="diffchange diffchange-inline"></strong> </del>A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.<del class="diffchange diffchange-inline"></p><p><strong></del>Failed End Condition:<del class="diffchange diffchange-inline"></strong> </del>Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.<del class="diffchange diffchange-inline"></p><p><strong></del>Trigger:<del class="diffchange diffchange-inline"></strong></p><p></del>A Yocto user<del class="diffchange diffchange-inline">&nbsp;</del>executes a build.<del class="diffchange diffchange-inline"></p><p>&nbsp;</p><p></del>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.<del class="diffchange diffchange-inline"></p></del></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Title:<ins class="diffchange diffchange-inline">''' </ins>Yocto Build System</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Background:<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Note: This is not a detailed background. You are encouraged to read up on the Yocto Project by using the following link: http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The Yocto Project provides a build system which can be used to provide, as an example, a file system/kernel/boot loader image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Primary Actors:<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Yocto User: Receives a Yocto build for a device. Executes the build.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>the Yocto Project: Provides the Yocto build system.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Build System Provider: They provide a Yocto based build, for example for their product. They may also provide patches to Packages that the recipes pull or may even add their own packages.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Goal in Context:<ins class="diffchange diffchange-inline">''' </ins>To execute a Yocto based build and generate an image for a hardware device or simulator and to have SPDX documents that describe the licensing for all copyrightable artifacts pulled in by the build system and used to generate that image (i.e. not just artifacts that make it into the image, everything and everything that it pulls including the build system). Note: envision we could be talking about 1000's of related SPDX documents</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Stakeholders and Interests:<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Yocto User:</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>A. To receive accurate and clear information of licensing for all copyrightable</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>elements used in the build and for the build system.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>B. To be able to comply easily with licenses for all copyrightable elements used in</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>the build and the build system.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>2. Package Maintainer:</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>A. To communicate the license information for their package.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>B. To have their licenses respected.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>3. the Yocto Project:</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>A. To communicate the license information for their build system and the licensing of each package</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>(currently via the license field in a recipe).</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>B. To have their licenses respected.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>4. Build System Provider:</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>A. To communicate the licensing information for the build they are providing.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>B. To comply with all the licenses used in the build the system they are providing.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Preconditions:<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline"># </ins>A yocoto build is created.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline"># </ins>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline"># </ins>A patch for a package used in the build is created.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Main Success Scenario:<ins class="diffchange diffchange-inline">''' </ins>A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Failed End Condition:<ins class="diffchange diffchange-inline">''' </ins>Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">'''</ins>Trigger:<ins class="diffchange diffchange-inline">'''</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>A Yocto user executes a build.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[[Category:Technical]]</ins></div></td></tr>
</table>MartinMichlmayrhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1878&oldid=prevBschineller at 18:42, 11 September 20122012-09-11T18:42:01Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 18:42, 11 September 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Yocto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide, as an example, a file system/kernel/boot loader image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p><strong>Primary Actors:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a&nbsp; Yocto based build, for example for their product. They may also provide patches to Packages that the recipes pull or may even add their own packages.</p><p><strong>Goal in Context:</strong>&nbsp; To execute a Yocto based build and generate an image for a hardware device or simulator&nbsp; and to have SPDX documents that describe the licensing for all copyrightable artifacts used to generate that image and <del class="diffchange diffchange-inline">for </del>the build system <del class="diffchange diffchange-inline">as well</del>.</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (currently via the license field in a recipe).</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Yocto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide, as an example, a file system/kernel/boot loader image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p><strong>Primary Actors:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a&nbsp; Yocto based build, for example for their product. They may also provide patches to Packages that the recipes pull or may even add their own packages.</p><p><strong>Goal in Context:</strong>&nbsp; To execute a Yocto based build and generate an image for a hardware device or simulator&nbsp; and to have SPDX documents that describe the licensing for all copyrightable artifacts <ins class="diffchange diffchange-inline">pulled in by the build system and </ins>used to generate that image <ins class="diffchange diffchange-inline">(i.e. not just artifacts that make it into the image, everything </ins>and <ins class="diffchange diffchange-inline">everything that it pulls including </ins>the build system<ins class="diffchange diffchange-inline">)</ins>. <ins class="diffchange diffchange-inline">&nbsp;Note: envision we could be talking about 1000's of related SPDX documents</ins></p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (currently via the license field in a recipe).</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td></tr>
</table>Bschinellerhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1877&oldid=prevJackM at 15:07, 6 June 20122012-06-06T15:07:44Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 15:07, 6 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the <del class="diffchange diffchange-inline">Ycoto </del>Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide, as an example, a file system/kernel/boot loader image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p><strong>Primary Actors:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a&nbsp; Yocto based build, for example for their product. They may also provide patches to Packages that the recipes pull or may even add their own packages.</p><p><strong>Goal in Context:</strong>&nbsp; To execute a Yocto based build and generate an image for a hardware device or simulator&nbsp; and to have SPDX documents that describe the licensing for all copyrightable artifacts used to generate that image and for the build system as well.</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (currently via the license field in a recipe).</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the <ins class="diffchange diffchange-inline">Yocto </ins>Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide, as an example, a file system/kernel/boot loader image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p><strong>Primary Actors:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a&nbsp; Yocto based build, for example for their product. They may also provide patches to Packages that the recipes pull or may even add their own packages.</p><p><strong>Goal in Context:</strong>&nbsp; To execute a Yocto based build and generate an image for a hardware device or simulator&nbsp; and to have SPDX documents that describe the licensing for all copyrightable artifacts used to generate that image and for the build system as well.</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (currently via the license field in a recipe).</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td></tr>
</table>JackMhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1876&oldid=prevJackM at 15:46, 5 June 20122012-06-05T15:46:30Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 15:46, 5 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System <del class="diffchange diffchange-inline">(the Yocto Project)</del></p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide a file system/kernel image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.<del class="diffchange diffchange-inline">&nbsp;</p><p></del>&nbsp;</p><p><strong>Primary <del class="diffchange diffchange-inline">Actor</del>:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a <del class="diffchange diffchange-inline">particular </del>build <del class="diffchange diffchange-inline">system</del>, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To <del class="diffchange diffchange-inline">generate </del>a <del class="diffchange diffchange-inline">kernel/file system&nbsp;</del>image for a hardware device or simulator <del class="diffchange diffchange-inline">using Yocto </del>and to have SPDX documents that describe the licensing for all copyrightable artifacts<del class="diffchange diffchange-inline">,</del></p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span> <del class="diffchange diffchange-inline">via</del></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the license field in a recipe.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide<ins class="diffchange diffchange-inline">, as an example, </ins>a file system/kernel<ins class="diffchange diffchange-inline">/boot loader </ins>image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in a package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p><strong>Primary <ins class="diffchange diffchange-inline">Actors</ins>:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a<ins class="diffchange diffchange-inline">&nbsp; Yocto based </ins>build, for example for their product. They may also provide patches to Packages that the recipes pull <ins class="diffchange diffchange-inline">or may even add their own packages</ins>.</p><p><strong>Goal in Context:</strong>&nbsp; To <ins class="diffchange diffchange-inline">execute </ins>a <ins class="diffchange diffchange-inline">Yocto based build and generate an </ins>image for a hardware device or simulator<ins class="diffchange diffchange-inline">&nbsp; </ins>and to have SPDX documents that describe the licensing for all copyrightable artifacts <ins class="diffchange diffchange-inline">used to generate that image and for the build system as well.</ins></p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <ins class="diffchange diffchange-inline">(currently via </ins>the license field in a recipe<ins class="diffchange diffchange-inline">)</ins>.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.<ins class="diffchange diffchange-inline"></p><p>&nbsp;</ins></p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td></tr>
</table>JackMhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1875&oldid=prevJackM at 14:26, 5 June 20122012-06-05T14:26:28Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 14:26, 5 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System (the Yocto Project)</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide a file system/kernel image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span> via</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the license field in a recipe.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System (the Yocto Project)</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide a file system/kernel image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in <ins class="diffchange diffchange-inline">a </ins>package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes the build.</p><p>Package Maintainer: These are upstream projects that a Yocto based build consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as having a secondary interest in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system.</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. the Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <span style="text-decoration: underline;">the licensing of each package</span> via</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the license field in a recipe.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected.</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p><strong>Preconditions:</strong></p><ol><li>A yocoto build is created.</li><li>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</li><li>A patch for a package used in the build is created.</li></ol><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project.</p></div></td></tr>
</table>JackMhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1874&oldid=prevJackM at 14:25, 5 June 20122012-06-05T14:25:58Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 14:25, 5 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System (the Yocto Project)</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a> </p><p>The Yocto Project provides a build system which can be used to provide a file system/kernel image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes <del class="diffchange diffchange-inline">a </del>build</p><p>Package Maintainer: These are upstream projects that <del class="diffchange diffchange-inline">have projects that </del>Yocto consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as a secondary <del class="diffchange diffchange-inline">actor </del>in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and the licensing of each package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.<del class="diffchange diffchange-inline"></p><p>&nbsp;</del></p><p><strong>Preconditions:</strong><del class="diffchange diffchange-inline">&nbsp;</del></p><<del class="diffchange diffchange-inline">p</del>><del class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp; 1. </del>A yocoto build is created.</<del class="diffchange diffchange-inline">p</del>><<del class="diffchange diffchange-inline">p</del>><del class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp; 2. </del>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</<del class="diffchange diffchange-inline">p</del>><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto Build System (the Yocto Project)</p><p><strong>Background:</strong>&nbsp;</p><p>Note: This is not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a></p><p>The Yocto Project provides a build system which can be used to provide a file system/kernel image that can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT, a tarball, patches and so forth. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.Whenever a build is executed, it is possible that the files in package are updated (added, modified, removed, etc).</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Receives a Yocto build for a device. Executes <ins class="diffchange diffchange-inline">the </ins>build<ins class="diffchange diffchange-inline">.</ins></p><p>Package Maintainer: These are upstream projects that <ins class="diffchange diffchange-inline">a </ins>Yocto <ins class="diffchange diffchange-inline">based build </ins>consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as <ins class="diffchange diffchange-inline">having </ins>a secondary <ins class="diffchange diffchange-inline">interest </ins>in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>the Yocto Project: Provides the Yocto build system<ins class="diffchange diffchange-inline">.</ins></p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. <ins class="diffchange diffchange-inline">the </ins>Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and <ins class="diffchange diffchange-inline"><span style="text-decoration: underline;"></ins>the licensing of each package<ins class="diffchange diffchange-inline"></span> via</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the license field in a recipe</ins>.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected<ins class="diffchange diffchange-inline">.</ins></p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p><strong>Preconditions:</strong></p><<ins class="diffchange diffchange-inline">ol><li</ins>>A yocoto build is created.</<ins class="diffchange diffchange-inline">li</ins>><<ins class="diffchange diffchange-inline">li</ins>>Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</<ins class="diffchange diffchange-inline">li><li>A patch for a package used in the build is created.</li></ol</ins>><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build<ins class="diffchange diffchange-inline">.</p><p>&nbsp;</p><p>Note: I forgot a point around RPMs when doing this and need to follow up again with the Yocto Project</ins>.</p></div></td></tr>
</table>JackMhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1873&oldid=prevJackM at 14:04, 5 June 20122012-06-05T14:04:05Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 14:04, 5 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto</p><p><strong>Background:</strong>&nbsp;</p><p><del class="diffchange diffchange-inline">Yocto </del>is a build system which <del class="diffchange diffchange-inline">typically provides </del>a file system/kernel image <del class="diffchange diffchange-inline">which </del>can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as<del class="diffchange diffchange-inline">: </del>source code control system like GIT <del class="diffchange diffchange-inline">or&nbsp;</del>a tarball. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p<del class="diffchange diffchange-inline">>Also see <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a</del>>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Executes a build</p><p>Package Maintainer: These are upstream projects that have projects that Yocto consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as a secondary actor in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>Yocto Project: Provides the Yocto build system</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and the licensing of each package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong>&nbsp;</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 1. A yocoto build is created. </p><p>&nbsp;&nbsp;&nbsp;&nbsp; 2. Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</p><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong><br /></strong></p><p><strong>Title:</strong>&nbsp; Yocto <ins class="diffchange diffchange-inline">Build System (the Yocto Project)</ins></p><p><strong>Background:</strong>&nbsp;</p><p><ins class="diffchange diffchange-inline">Note: This </ins>is <ins class="diffchange diffchange-inline">not a detailed background. You are encouraged&nbsp; to read up on the Ycoto Project by using the following link:&nbsp; <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a> </p><p>The Yocto Project provides </ins>a build system which <ins class="diffchange diffchange-inline">can be used to provide </ins>a file system/kernel image <ins class="diffchange diffchange-inline">that </ins>can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as source code control system like GIT<ins class="diffchange diffchange-inline">, </ins>a tarball<ins class="diffchange diffchange-inline">, patches and so forth</ins>. Entities providng a Yocto build for their hardware may also be providing pacthes for the package<ins class="diffchange diffchange-inline">.Whenever a build is executed, it is possible that the files in package are updated (added, modified, removed, etc)</ins>.</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: <ins class="diffchange diffchange-inline">Receives a Yocto build for a device. </ins>Executes a build</p><p>Package Maintainer: These are upstream projects that have projects that Yocto consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as a secondary actor in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p><ins class="diffchange diffchange-inline">the </ins>Yocto Project: Provides the Yocto build system</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and the licensing of each package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong>&nbsp;</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 1. A yocoto build is created.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 2. Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</p><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> A user executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p></div></td></tr>
</table>JackMhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1872&oldid=prevJackM at 13:39, 5 June 20122012-06-05T13:39:27Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 13:39, 5 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p><strong>Title:</strong>&nbsp; Yocto</p><p><strong>Background:</strong>&nbsp;</p><p>Yocto is a build system which typically provides a file system/kernel image which can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as: source code control system like GIT or&nbsp;a tarball. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>Also see <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Executes a build</p><p>Package Maintainer: These are upstream projects that have projects that Yocto consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as a secondary actor in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>Yocto Project: Provides the Yocto build system</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and the licensing of each package. </p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong>&nbsp;</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 1. A yocoto build is created.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 2. Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</p><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> <del class="diffchange diffchange-inline">Someone </del>executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline"><p><strong><br /></strong></p></ins><p><strong>Title:</strong>&nbsp; Yocto</p><p><strong>Background:</strong>&nbsp;</p><p>Yocto is a build system which typically provides a file system/kernel image which can be downloaded onto a device and executed. When Yocto builds a package the package source can come from various sources such as: source code control system like GIT or&nbsp;a tarball. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>Also see <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: Executes a build</p><p>Package Maintainer: These are upstream projects that have projects that Yocto consumes. This upstream project could be a company that provides a package as well. A Package Maintainer could be viewed as a secondary actor in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto.</p><p>Yocto Project: Provides the Yocto build system</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all copyrightable artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and the build system.</p><p><br /> 2. Package Maintainer:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</p><p>&nbsp;</p><p>3. Yocto Project:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and the licensing of each package.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected</p><p>&nbsp;</p><p>4. Build System Provider:</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the licensing information for the build they are providing.</p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To comply with all the licenses used in the build the system they are providing.</p><p>&nbsp;</p><p><strong>Preconditions:</strong>&nbsp;</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 1. A yocoto build is created. </p><p>&nbsp;&nbsp;&nbsp;&nbsp; 2. Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</p><p>&nbsp;</p><p><strong>Main Success Scenario:</strong> <ins class="diffchange diffchange-inline">A user </ins>executing a Yocto based build gets SPDX documents that describe the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> Inaccurate or incomplete licensing information is provided for all packages used in the build and/or for the Yocto build system.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p></div></td></tr>
</table>JackMhttps://wiki.spdx.org/index.php?title=Technical_Team/Use_Cases/2.0/Build_System_Yocto&diff=1871&oldid=prevJackM at 13:38, 5 June 20122012-06-05T13:38:09Z<p></p>
<table class='diff diff-contentalign-left'>
<col class='diff-marker' />
<col class='diff-content' />
<col class='diff-marker' />
<col class='diff-content' />
<tr style='vertical-align: top;'>
<td colspan='2' style="background-color: white; color:black; text-align: center;">← Older revision</td>
<td colspan='2' style="background-color: white; color:black; text-align: center;">Revision as of 13:38, 5 June 2012</td>
</tr><tr><td colspan="2" class="diff-lineno">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><p <del class="diffchange diffchange-inline">class="MsoNormal"><strong>THis is still a draft and not quite finiliazed but its close.</strong></p><p class="MsoNormal"</del>><strong>Title:</strong>&nbsp; Yocto</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Background:</strong>&nbsp;</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>When Yocto builds a package the package source can come from various sources such as: source code control system like GIT or&nbsp;a tarball. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>Also see <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a>&nbsp;</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Primary Actor:</strong></p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>Yocto User: <del class="diffchange diffchange-inline">Executs </del>a build</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>Package Maintainer: These are upstream projects <del class="diffchange diffchange-inline">thatr </del>have projects that Yocto consumes. This upstream project could be a company that provides a package as well.</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>Yocto Project: Provides the Yocto build system</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><del class="diffchange diffchange-inline">Yocto </del>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all <del class="diffchange diffchange-inline">copyrigthable </del>artifacts,</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Stakeholders and Interests:</strong>&nbsp;</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>Yocto User: <del class="diffchange diffchange-inline">Genetrates a buuod getting an image for their hardware. They want SPDX documents for each package/coyrightable element.</del></p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><<del class="diffchange diffchange-inline">br </del>/><del class="diffchange diffchange-inline">Package Maintainer: To</del>&nbsp;<del class="diffchange diffchange-inline">provide license information using SPDX</del></p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><<del class="diffchange diffchange-inline">br </del>/><del class="diffchange diffchange-inline">Yocto Project: To provide SPDX documents that describe the licensing of the artifacts</del>&nbsp;<del class="diffchange diffchange-inline">provided by </del>the build system.</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><br /><del class="diffchange diffchange-inline">Build System Provider</del>: <del class="diffchange diffchange-inline">They provide a particular build system for thier hardware, for example </del>for their <del class="diffchange diffchange-inline">product. They may also provide patches to Packages that the recipes pull</del>.</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><<del class="diffchange diffchange-inline">strong</del>><del class="diffchange diffchange-inline">Providers of artifacts:</del>&nbsp;</<del class="diffchange diffchange-inline">strong</del>><<del class="diffchange diffchange-inline">/</del>p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><<del class="diffchange diffchange-inline">strong</del>><del class="diffchange diffchange-inline">Consumers </del>of <del class="diffchange diffchange-inline">artifacts:</del></<del class="diffchange diffchange-inline">strong</del>></p><<del class="diffchange diffchange-inline">ol type="1"</del>><<del class="diffchange diffchange-inline">li class="MsoNormal"</del>><del class="diffchange diffchange-inline">To receive accurate and clear information of licensing of artifacts</del></<del class="diffchange diffchange-inline">li</del>><<del class="diffchange diffchange-inline">li class="MsoNormal"</del>>To <del class="diffchange diffchange-inline">be able to comply easily with licenses </del>for <del class="diffchange diffchange-inline">artifacts</del></<del class="diffchange diffchange-inline">li</del>><<del class="diffchange diffchange-inline">li class="MsoNormal"</del>>To <del class="diffchange diffchange-inline">be able to subset, extend, or aggregate artifacts and pass on clear authoritative verifiable license for </del>the <del class="diffchange diffchange-inline">resulting new copyrightable artifacts</del>.</<del class="diffchange diffchange-inline">li</del>></<del class="diffchange diffchange-inline">ol</del>><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Preconditions:</strong>&nbsp;</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Main Success Scenario:</strong> Someone executing a Yocto based build gets SPDX documents that <del class="diffchange diffchange-inline">decsribe </del>the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Failed End Condition:</strong> <del class="diffchange diffchange-inline">SPDX documents </del>for <del class="diffchange diffchange-inline">copyrigthable elements are missing</del>.<del class="diffchange diffchange-inline">ow easy will be tis to detect as these builds can be rather large?</del></p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>><strong>Trigger:</strong></p><p <del class="diffchange diffchange-inline">class="MsoNormal"</del>>A Yocto user&nbsp;executes a build.</p></div></td><td class='diff-marker'>+</td><td style="color:black; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><p><strong>Title:</strong>&nbsp; Yocto</p><p><strong>Background:</strong>&nbsp;</p><p><ins class="diffchange diffchange-inline">Yocto is a build system which typically provides a file system/kernel image which can be downloaded onto a device and executed. </ins>When Yocto builds a package the package source can come from various sources such as: source code control system like GIT or&nbsp;a tarball. Entities providng a Yocto build for their hardware may also be providing pacthes for the package.</p><p>Yocto uses recipes to build packages. These recipes do contain a License field. The current short names do not match SPDX short names and likely will not. It was rather difficult to get alignment on the current ones used. There is talk on the Yocto project about converting the Yocto short names into SPDX ones.&nbsp;</p><p>Also see <a href="http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html">http://www.yoctoproject.org/docs/1.0/yocto-quick-start/yocto-project-qs.html</a>&nbsp;</p><p><strong>Primary Actor:</strong></p><p>Yocto User: <ins class="diffchange diffchange-inline">Executes </ins>a build</p><p>Package Maintainer: These are upstream projects <ins class="diffchange diffchange-inline">that </ins>have projects that Yocto consumes. This upstream project could be a company that provides a package as well<ins class="diffchange diffchange-inline">. A Package Maintainer could be viewed as a secondary actor in this use case as their package may be consumed by a Yocto build even though they as packages maintainers have no vested interest in Yocto</ins>.</p><p>Yocto Project: Provides the Yocto build system</p><p>Build System Provider: They provide a particular build system, for example for their product. They may also provide patches to Packages that the recipes pull.</p><p><strong>Goal in Context:</strong>&nbsp; To generate a kernel/file system&nbsp;image for a hardware device or simulator using Yocto and to have SPDX documents that describe the licensing for all <ins class="diffchange diffchange-inline">copyrightable </ins>artifacts,</p><p><strong>Stakeholders and Interests:</strong>&nbsp;</p><p>Yocto User:</p><p><ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To receive accurate and clear information of licensing for all copyrightable</ins></<ins class="diffchange diffchange-inline">p><p</ins>>&nbsp;<ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; elements used in the build and for the build system.</ins></p><p><ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To be able to comply easily with licenses for all copyrightable elements used in</ins></<ins class="diffchange diffchange-inline">p><p</ins>>&nbsp;<ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;the build and </ins>the build system.</p><p><br /> <ins class="diffchange diffchange-inline">2. Package Maintainer</ins>:<ins class="diffchange diffchange-inline"></p><p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information </ins>for their <ins class="diffchange diffchange-inline">package</ins>.</p><p><ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. To have their licenses respected.</ins><<ins class="diffchange diffchange-inline">/p><p</ins>>&nbsp;</<ins class="diffchange diffchange-inline">p</ins>><p><ins class="diffchange diffchange-inline">3. Yocto Project:</ins><<ins class="diffchange diffchange-inline">/</ins>p><<ins class="diffchange diffchange-inline">p</ins>><ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. To communicate the license information for their build system and the licensing </ins>of <ins class="diffchange diffchange-inline">each package. </ins></<ins class="diffchange diffchange-inline">p</ins>><ins class="diffchange diffchange-inline"><p>&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;B. To have their licenses respected</ins></p><<ins class="diffchange diffchange-inline">p</ins>><ins class="diffchange diffchange-inline">&nbsp;</ins><<ins class="diffchange diffchange-inline">/p</ins>><ins class="diffchange diffchange-inline"><p>4. Build System Provider:</ins></<ins class="diffchange diffchange-inline">p</ins>><<ins class="diffchange diffchange-inline">p</ins>><ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A. </ins>To <ins class="diffchange diffchange-inline">communicate the licensing information </ins>for <ins class="diffchange diffchange-inline">the build they are providing.</ins></<ins class="diffchange diffchange-inline">p</ins>><<ins class="diffchange diffchange-inline">p</ins>><ins class="diffchange diffchange-inline">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. </ins>To <ins class="diffchange diffchange-inline">comply with all </ins>the <ins class="diffchange diffchange-inline">licenses used in the build the system they are providing</ins>.</<ins class="diffchange diffchange-inline">p</ins>><ins class="diffchange diffchange-inline"><p>&nbsp;</ins></<ins class="diffchange diffchange-inline">p</ins>><p><strong>Preconditions:</strong>&nbsp;</p><p<ins class="diffchange diffchange-inline">>&nbsp;&nbsp;&nbsp;&nbsp; 1. A yocoto build is created.</p><p>&nbsp;&nbsp;&nbsp;&nbsp; 2. Packages used in the Yocoto build have SPDX documents describing the copyrigthable elements of the package.</p><p>&nbsp;</p><p</ins>><strong>Main Success Scenario:</strong> Someone executing a Yocto based build gets SPDX documents that <ins class="diffchange diffchange-inline">describe </ins>the licensing for all copyrightable elements that were used to create the build and are the result of a build.</p><p><strong>Failed End Condition:</strong> <ins class="diffchange diffchange-inline">Inaccurate or incomplete licensing information is provided </ins>for <ins class="diffchange diffchange-inline">all packages used in the build and/or for the Yocto build system</ins>.</p><p><strong>Trigger:</strong></p><p>A Yocto user&nbsp;executes a build.</p></div></td></tr>
</table>JackM