mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00
Code Issues Projects Releases Wiki Activity

sdk-manual: Edits to "License Detection"

Browse Source 
Updates to prose for better understanding.

(From yocto-docs rev: 44a07560845c973a0da4c27969c740d3d712d323)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-31 10:10:20 -07:00
committed by Richard Purdie
parent 290809334a
commit 73c7e9d229
1 changed files with 17 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/sdk-manual/sdk-extensible.xml
+17 -14
View File
@@ -1157,20 +1157,24 @@
<para> <para>
The <filename>devtool add</filename> command attempts to The <filename>devtool add</filename> command attempts to
determine if the software you are adding is able to be determine if the software you are adding is able to be
distributed under a common open-source license and sets the distributed under a common, open-source license.
If so, the command sets the
<ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE'><filename>LICENSE</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE'><filename>LICENSE</filename></ulink>
value accordingly. value accordingly.
You should double-check this value against the documentation You should double-check the value added by the command against
or source files for the software you are building and update the documentation or source files for the software you are
that <filename>LICENSE</filename> value if necessary. building and, if necessary, update that
<filename>LICENSE</filename> value.
</para> </para>
<para> <para>
The <filename>devtool add</filename> command also sets the The <filename>devtool add</filename> command also sets the
<ulink url='&YOCTO_DOCS_REF_URL;#var-LIC_FILES_CHKSUM'><filename>LIC_FILES_CHKSUM</filename></ulink> <ulink url='&YOCTO_DOCS_REF_URL;#var-LIC_FILES_CHKSUM'><filename>LIC_FILES_CHKSUM</filename></ulink>
value to point to all files that appear to be license-related. value to point to all files that appear to be license-related.
However, license statements often appear in comments at the top Realize that license statements often appear in comments at
of source files or within documentation. the top of source files or within the documentation.
In such cases, the command does not recognize those license
statements.
Consequently, you might need to amend the Consequently, you might need to amend the
<filename>LIC_FILES_CHKSUM</filename> variable to point to one <filename>LIC_FILES_CHKSUM</filename> variable to point to one
or more of those comments if present. or more of those comments if present.
@@ -1184,14 +1188,13 @@
<para> <para>
If the <filename>devtool add</filename> command cannot If the <filename>devtool add</filename> command cannot
determine licensing information, the determine licensing information, <filename>devtool</filename>
<filename>LICENSE</filename> value is set to "CLOSED" and the sets the <filename>LICENSE</filename> value to "CLOSED" and
<filename>LIC_FILES_CHKSUM</filename> value remains unset. leaves the <filename>LIC_FILES_CHKSUM</filename> value unset.
This behavior allows you to continue with development but is This behavior allows you to continue with development even
unlikely to be correct in all cases. though the settings are unlikely to be correct in all cases.
Consequently, you should check the documentation or source You should check the documentation or source files for the
files for the software you are building to determine the actual software you are building to determine the actual license.
license.
</para> </para>
</section> </section>