1 files changed, 1 insertions, 107 deletions
diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml
index f88e2a1dbf..56b806de0b 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -9,8 +9,7 @@
        software packages, extending or customizing images or porting the Yocto Project to
        new hardware (adding a new machine). 
        The chapter also describes ways to modify package source code, combine multiple 
-        versions of library files into a single image, track license changes, and handle
+        versions of library files into a single image, and handle a package name alias.
-        a package name alias.
        Finally, the chapter contains advice about how to make changes to the 
        Yocto Project to achieve the best results.
    </para>
@@ -919,111 +918,6 @@
        </section> 
    </section>
-    <section id="usingpoky-configuring-LIC_FILES_CHKSUM">
-        <title>Tracking License Changes</title>
-        <para>
-            The license of an upstream project might change in the future. In order to prevent these changes
-            going unnoticed, the Yocto Project provides a 
-            <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename>
-            variable to track changes to the license text. The checksums are validated at the end of the
-            configure step, and if the checksums do not match, the build will fail.
-        </para>
-        <section id="usingpoky-specifying-LIC_FILES_CHKSUM">
-            <title>Specifying the <filename>LIC_FILES_CHKSUM</filename> Variable</title>
-            <para>
-                The <filename>LIC_FILES_CHKSUM</filename>
-                variable contains checksums of the license text in the source code for the recipe.
-                Following is an example of how to specify <filename>LIC_FILES_CHKSUM</filename>:
-                <literallayout class='monospaced'>
-     LIC_FILES_CHKSUM = "file://COPYING;md5=xxxx \
-                         file://licfile1.txt;beginline=5;endline=29;md5=yyyy \
-                         file://licfile2.txt;endline=50;md5=zzzz \
-                         ..."
-                </literallayout>
-            </para>
-            <para>
-                The Yocto Project uses the 
-                <filename><link linkend='var-S'>S</link></filename> variable as the 
-                default directory used when searching files listed in 
-                <filename>LIC_FILES_CHKSUM</filename>.
-                The previous example employs the default directory.
-            </para>
-            <para>
-                You can also use relative paths as shown in the following example: 
-                <literallayout class='monospaced'>
-     LIC_FILES_CHKSUM = "file://src/ls.c;startline=5;endline=16;\
-                                         md5=bb14ed3c4cda583abc85401304b5cd4e"
-     LIC_FILES_CHKSUM = "file://../license.html;md5=5c94767cedb5d6987c902ac850ded2c6"
-                </literallayout>
-            </para>
-            <para>
-                In this example, the first line locates a file in 
-                <filename><link linkend='var-S'>S</link>/src/ls.c</filename>. 
-                The second line refers to a file in 
-                <filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>, which is the parent
-                of <filename>S</filename>.
-            </para>
-            <para>
-                Note that this variable is mandatory for all recipes, unless the 
-                <filename>LICENSE</filename> variable is set to "CLOSED".
-            </para>
-        </section>
-        <section id="usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax">
-            <title>Explanation of Syntax</title>
-            <para>
-                As mentioned in the previous section, the 
-                <filename>LIC_FILES_CHKSUM</filename> variable lists all the 
-                important files that contain the license text for the source code. 
-                It is possible to specify a checksum for an entire file, or a specific section of a
-                file (specified by beginning and ending line numbers with the "beginline" and "endline"
-                parameters, respectively). 
-                The latter is useful for source files with a license notice header,
-                README documents, and so forth.
-                If you do not use the "beginline" parameter, then it is assumed that the text begins on the 
-                first line of the file. 
-                Similarly, if you do not use the "endline" parameter, it is assumed that the license text 
-                ends with the last line of the file. 
-            </para>
-            <para>
-                The "md5" parameter stores the md5 checksum of the license text. 
-                If the license text changes in any way as compared to this parameter
-                then a mismatch occurs.
-                This mismatch triggers a build failure and notifies the developer.
-                Notification allows the developer to review and address the license text changes.
-                Also note that if a mismatch occurs during the build, the correct md5 
-                checksum is placed in the build log and can be easily copied to the recipe.
-            </para>
-            <para>
-                There is no limit to how many files you can specify using the 
-                <filename>LIC_FILES_CHKSUM</filename> variable.
-                Generally, however, every project requires a few specifications for license tracking. 
-                Many projects have a "COPYING" file that stores the license information for all the source 
-                code files.
-                This practice allows you to just track the "COPYING" file as long as it is kept up to date. 
-            </para>
-            <tip>
-                If you specify an empty or invalid "md5" parameter, BitBake returns an md5 mis-match 
-                error and displays the correct "md5" parameter value during the build. 
-                The correct parameter is also captured in the build log. 
-            </tip>
-            <tip>
-                If the whole file contains only license text, you do not need to use the "beginline" and 
-                "endline" parameters. 
-            </tip>
-        </section>
-    </section>
    <section id="usingpoky-configuring-DISTRO_PN_ALIAS">
        <title>Handling a Package Name Alias</title>
        <para>

diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml index f88e2a1dbf..56b806de0b 100644 --- a/documentation/poky-ref-manual/extendpoky.xml +++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -9,8 +9,7 @@
9	software packages, extending or customizing images or porting the Yocto Project to	9	software packages, extending or customizing images or porting the Yocto Project to
10	new hardware (adding a new machine).	10	new hardware (adding a new machine).
11	The chapter also describes ways to modify package source code, combine multiple	11	The chapter also describes ways to modify package source code, combine multiple
12	versions of library files into a single image, track license changes, and handle	12	versions of library files into a single image, and handle a package name alias.
13	a package name alias.
14	Finally, the chapter contains advice about how to make changes to the	13	Finally, the chapter contains advice about how to make changes to the
15	Yocto Project to achieve the best results.	14	Yocto Project to achieve the best results.
16	</para>	15	</para>
@@ -919,111 +918,6 @@
919	</section>	918	</section>
920	</section>	919	</section>
921		920
922	<section id="usingpoky-configuring-LIC_FILES_CHKSUM">
923	<title>Tracking License Changes</title>
924
925	<para>
926	The license of an upstream project might change in the future. In order to prevent these changes
927	going unnoticed, the Yocto Project provides a
928	<filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename>
929	variable to track changes to the license text. The checksums are validated at the end of the
930	configure step, and if the checksums do not match, the build will fail.
931	</para>
932
933	<section id="usingpoky-specifying-LIC_FILES_CHKSUM">
934	<title>Specifying the <filename>LIC_FILES_CHKSUM</filename> Variable</title>
935
936	<para>
937	The <filename>LIC_FILES_CHKSUM</filename>
938	variable contains checksums of the license text in the source code for the recipe.
939	Following is an example of how to specify <filename>LIC_FILES_CHKSUM</filename>:
940	<literallayout class='monospaced'>
941	LIC_FILES_CHKSUM = "file://COPYING;md5=xxxx \
942	file://licfile1.txt;beginline=5;endline=29;md5=yyyy \
943	file://licfile2.txt;endline=50;md5=zzzz \
944	..."
945	</literallayout>
946	</para>
947
948	<para>
949	The Yocto Project uses the
950	<filename><link linkend='var-S'>S</link></filename> variable as the
951	default directory used when searching files listed in
952	<filename>LIC_FILES_CHKSUM</filename>.
953	The previous example employs the default directory.
954	</para>
955
956	<para>
957	You can also use relative paths as shown in the following example:
958	<literallayout class='monospaced'>
959	LIC_FILES_CHKSUM = "file://src/ls.c;startline=5;endline=16;\
960	md5=bb14ed3c4cda583abc85401304b5cd4e"
961	LIC_FILES_CHKSUM = "file://../license.html;md5=5c94767cedb5d6987c902ac850ded2c6"
962	</literallayout>
963	</para>
964
965	<para>
966	In this example, the first line locates a file in
967	<filename><link linkend='var-S'>S</link>/src/ls.c</filename>.
968	The second line refers to a file in
969	<filename><link linkend='var-WORKDIR'>WORKDIR</link></filename>, which is the parent
970	of <filename>S</filename>.
971	</para>
972	<para>
973	Note that this variable is mandatory for all recipes, unless the
974	<filename>LICENSE</filename> variable is set to "CLOSED".
975	</para>
976	</section>
977
978	<section id="usingpoky-LIC_FILES_CHKSUM-explanation-of-syntax">
979	<title>Explanation of Syntax</title>
980	<para>
981	As mentioned in the previous section, the
982	<filename>LIC_FILES_CHKSUM</filename> variable lists all the
983	important files that contain the license text for the source code.
984	It is possible to specify a checksum for an entire file, or a specific section of a
985	file (specified by beginning and ending line numbers with the "beginline" and "endline"
986	parameters, respectively).
987	The latter is useful for source files with a license notice header,
988	README documents, and so forth.
989	If you do not use the "beginline" parameter, then it is assumed that the text begins on the
990	first line of the file.
991	Similarly, if you do not use the "endline" parameter, it is assumed that the license text
992	ends with the last line of the file.
993	</para>
994
995	<para>
996	The "md5" parameter stores the md5 checksum of the license text.
997	If the license text changes in any way as compared to this parameter
998	then a mismatch occurs.
999	This mismatch triggers a build failure and notifies the developer.
1000	Notification allows the developer to review and address the license text changes.
1001	Also note that if a mismatch occurs during the build, the correct md5
1002	checksum is placed in the build log and can be easily copied to the recipe.
1003	</para>
1004
1005	<para>
1006	There is no limit to how many files you can specify using the
1007	<filename>LIC_FILES_CHKSUM</filename> variable.
1008	Generally, however, every project requires a few specifications for license tracking.
1009	Many projects have a "COPYING" file that stores the license information for all the source
1010	code files.
1011	This practice allows you to just track the "COPYING" file as long as it is kept up to date.
1012	</para>
1013
1014	<tip>
1015	If you specify an empty or invalid "md5" parameter, BitBake returns an md5 mis-match
1016	error and displays the correct "md5" parameter value during the build.
1017	The correct parameter is also captured in the build log.
1018	</tip>
1019
1020	<tip>
1021	If the whole file contains only license text, you do not need to use the "beginline" and
1022	"endline" parameters.
1023	</tip>
1024	</section>
1025	</section>
1026
1027	<section id="usingpoky-configuring-DISTRO_PN_ALIAS">	921	<section id="usingpoky-configuring-DISTRO_PN_ALIAS">
1028	<title>Handling a Package Name Alias</title>	922	<title>Handling a Package Name Alias</title>
1029	<para>	923	<para>