sdk-manual: Edits to "License Detection"

Updates to prose for better understanding.

(From yocto-docs rev: 5c4384d4311d8fbedad0eb9ebb77427a1dbbbdcf)

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 ace3fe02d1
commit b598e35761

View File

@@ -1157,20 +1157,24 @@
<para>
The <filename>devtool add</filename> command attempts to
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>
value accordingly.
You should double-check this value against the documentation
or source files for the software you are building and update
that <filename>LICENSE</filename> value if necessary.
You should double-check the value added by the command against
the documentation or source files for the software you are
building and, if necessary, update that
<filename>LICENSE</filename> value.
</para>
<para>
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>
value to point to all files that appear to be license-related.
However, license statements often appear in comments at the top
of source files or within documentation.
Realize that license statements often appear in comments at
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
<filename>LIC_FILES_CHKSUM</filename> variable to point to one
or more of those comments if present.
@@ -1184,14 +1188,13 @@
<para>
If the <filename>devtool add</filename> command cannot
determine licensing information, the
<filename>LICENSE</filename> value is set to "CLOSED" and the
<filename>LIC_FILES_CHKSUM</filename> value remains unset.
This behavior allows you to continue with development but is
unlikely to be correct in all cases.
Consequently, you should check the documentation or source
files for the software you are building to determine the actual
license.
determine licensing information, <filename>devtool</filename>
sets the <filename>LICENSE</filename> value to "CLOSED" and
leaves the <filename>LIC_FILES_CHKSUM</filename> value unset.
This behavior allows you to continue with development even
though the settings are unlikely to be correct in all cases.
You should check the documentation or source files for the
software you are building to determine the actual license.
</para>
</section>