summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-10-19 14:34:33 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-10-19 16:38:57 (GMT)
commite90d014a0a75b7cb7e3440062afac2e532a47d52 (patch)
treef9102e670efbaf96838f10810e2f4734edd44118 /documentation
parente7ecb7e61e38c0f002a6145d6518bed91fc93aaf (diff)
downloadpoky-e90d014a0a75b7cb7e3440062afac2e532a47d52.tar.gz
documentation: dev-manual - Updated compliance section.
Applied legal changes per Karen Copenhaver's suggestions. (From yocto-docs rev: 73b68aa349530f6604c7edc87b503f1b614b2c46) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml21
1 files changed, 11 insertions, 10 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 890ea6e..df64e11 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2618,7 +2618,7 @@
2618 While this section does not provide legal advice or 2618 While this section does not provide legal advice or
2619 comprehensively cover all scenarios, it does 2619 comprehensively cover all scenarios, it does
2620 present methods that you can use to 2620 present methods that you can use to
2621 meet the compliance requirements during a software 2621 assist you in meeting the compliance requirements during a software
2622 release. 2622 release.
2623 </para> 2623 </para>
2624 2624
@@ -2705,12 +2705,13 @@
2705 INHERIT += "${ARCHIVER_CLASS}" 2705 INHERIT += "${ARCHIVER_CLASS}"
2706 SOURCE_ARCHIVE_PACKAGE_TYPE = "tar" 2706 SOURCE_ARCHIVE_PACKAGE_TYPE = "tar"
2707 </literallayout> 2707 </literallayout>
2708 During the creation of your image, all needed source 2708 During the creation of your image, all GPL
2709 or other copyleft licensed source
2709 is placed within subdirectories of 2710 is placed within subdirectories of
2710 <filename>DEPLOY_DIR/sources</filename> based on the 2711 <filename>DEPLOY_DIR/sources</filename> based on the
2711 <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE'><filename>LICENSE</filename></ulink> 2712 <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE'><filename>LICENSE</filename></ulink>
2712 for each recipe. 2713 for each recipe.
2713 Releasing the entire directory ensures compliance with 2714 Releasing the entire directory enables you to comply with
2714 requirements concerning providing the unmodified source. 2715 requirements concerning providing the unmodified source.
2715 It is important to note that the size of the directory can 2716 It is important to note that the size of the directory can
2716 get large. 2717 get large.
@@ -2773,10 +2774,10 @@
2773 </para> 2774 </para>
2774 2775
2775 <para> 2776 <para>
2776 Providing compilation scripts and source code modifications 2777 By releasing the version of the OpenEmbedded build system
2777 can be addressed with one step. 2778 and the layers used during the build, you will be providing both
2778 All you need to do is ensure that you release the version of 2779 compilation scripts and the source code modifications in one
2779 the OpenEmbedded build system and the layers used during the build. 2780 step.
2780 </para> 2781 </para>
2781 2782
2782 <para> 2783 <para>
@@ -2785,8 +2786,8 @@
2785 and a distro layer, and those those layers are used to patch, 2786 and a distro layer, and those those layers are used to patch,
2786 compile, package, or modify (in any way) any open source 2787 compile, package, or modify (in any way) any open source
2787 software included in your released images, you 2788 software included in your released images, you
2788 must release those layers as required by section 3 of GPLv2 2789 may be required to to release those layers under section 3 of
2789 and section 1 of GPLv3. 2790 GPLv2 or section 1 of GPLv3.
2790 One way of doing that is with a clean 2791 One way of doing that is with a clean
2791 checkout of the version of the Yocto Project and layers used 2792 checkout of the version of the Yocto Project and layers used
2792 during your build. 2793 during your build.
@@ -2826,7 +2827,7 @@
2826 </literallayout> 2827 </literallayout>
2827 Creating and providing an archive of the metadata layers 2828 Creating and providing an archive of the metadata layers
2828 (recipes, configuration files, and so forth) 2829 (recipes, configuration files, and so forth)
2829 ensures that you have met your 2830 enables you to meet your
2830 requirements to include the scripts to control compilation 2831 requirements to include the scripts to control compilation
2831 as well as any modifications to the original source. 2832 as well as any modifications to the original source.
2832 </para> 2833 </para>