summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-02-07 10:06:17 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-02-19 06:59:51 -0800
commit90399afd5405006223a3d2da35bc69cd6b49ec71 (patch)
tree8fac0505f763e48e4000df8979fa045ed6f5011d
parente504de2cf456820ebf26735222dd6bdc269e7613 (diff)
downloadopenembedded-core-contrib-90399afd5405006223a3d2da35bc69cd6b49ec71.tar.gz
openembedded-core-contrib-90399afd5405006223a3d2da35bc69cd6b49ec71.tar.bz2
openembedded-core-contrib-90399afd5405006223a3d2da35bc69cd6b49ec71.zip
dev-manual: Minor corrections to maintaining Open Source lic. comp.
The section "Maintaining Open Source License Compliance During Your Product's Lifecycle" had a vew minor typo things (e.g. duplicated word and some formatting issues). I fixed these. (From yocto-docs rev: 67beb658445e79129d8aae1739bb33c000367107) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml22
1 files changed, 12 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 811c23e810..6cb0bcb5f1 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -10884,10 +10884,11 @@
<para>
Before you employ <filename>DL_DIR</filename> or the
- archiver class, you need to decide how you choose to
- provide source.
- The source archiver class can generate tarballs and SRPMs
- and can create them with various levels of compliance in mind.
+ <filename>archiver</filename> class, you need to decide how
+ you choose to provide source.
+ The source <filename>archiver</filename> class can generate
+ tarballs and SRPMs and can create them with various levels of
+ compliance in mind.
</para>
<para>
@@ -10982,9 +10983,9 @@
<ulink url='&YOCTO_DOCS_REF_URL;#var-COPY_LIC_DIRS'><filename>COPY_LIC_DIRS</filename></ulink>
and
<ulink url='&YOCTO_DOCS_REF_URL;#var-COPY_LIC_MANIFEST'><filename>COPY_LIC_MANIFEST</filename></ulink>
- add a copy of the license when the image is built but do not
- offer a path for adding licenses for newly installed packages
- to an image.
+ add a copy of the license when the image is built but do
+ not offer a path for adding licenses for newly installed
+ packages to an image.
<ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE_CREATE_PACKAGE'><filename>LICENSE_CREATE_PACKAGE</filename></ulink>
adds a separate package and an upgrade path for adding
licenses to an image.</para>
@@ -10992,7 +10993,8 @@
</para>
<para>
- As the source archiver has already archived the original
+ As the source <filename>archiver</filename> class has already
+ archived the original
unmodified source that contains the license files,
you would have already met the requirements for inclusion
of the license information with source as defined by the GPL
@@ -11004,7 +11006,7 @@
<title>Providing Compilation Scripts and Source Code Modifications</title>
<para>
- At this point, we have addressed all we need to address
+ At this point, we have addressed all we need to
prior to generating the image.
The next two requirements are addressed during the final
packaging of the release.
@@ -11023,7 +11025,7 @@
and a distro layer, and those those layers are used to patch,
compile, package, or modify (in any way) any open source
software included in your released images, you
- might be required to to release those layers under section 3 of
+ might be required to release those layers under section 3 of
GPLv2 or section 1 of GPLv3.
One way of doing that is with a clean
checkout of the version of the Yocto Project and layers used