summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/extendpoky.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-08-24 07:58:32 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-08-24 19:49:38 -0700
commitd02e56fd14026e2f51665631a50901fc568c731a (patch)
tree8ba09da577f6c5cae8a637370ab0c7531bc54ade /documentation/poky-ref-manual/extendpoky.xml
parent88dfc936dc37b316acdbcd1b12d37f93fe65eea7 (diff)
downloadpoky-d02e56fd14026e2f51665631a50901fc568c731a.tar.gz
documentation: Changes to Paul Eggleton's edits for various manuals.
Paul sent me a bunch of minor edits and technical corrections for the ADT, BSP, Development, and YP reference manual. Most changes were taken as he submitted them. However, some formatting conventions were not followed in the commits he made to yocto-docs/paule/docs2. After merging them to my yocto-docs/master branch I fixed some issues. (From yocto-docs rev: 93f4ea2dee976448f623953e801a80d59736450a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/extendpoky.xml')
-rw-r--r--documentation/poky-ref-manual/extendpoky.xml15
1 files changed, 8 insertions, 7 deletions
diff --git a/documentation/poky-ref-manual/extendpoky.xml b/documentation/poky-ref-manual/extendpoky.xml
index fdccbacd68..db15fc6178 100644
--- a/documentation/poky-ref-manual/extendpoky.xml
+++ b/documentation/poky-ref-manual/extendpoky.xml
@@ -1004,7 +1004,7 @@
1004 1004
1005 <para> 1005 <para>
1006 Finally, don't forget to 'bump' the 1006 Finally, don't forget to 'bump' the
1007 <glossterm><link linkend='var-PR'>PR</link></glossterm> value in the same recipe since 1007 <filename><link linkend='var-PR'>PR</link></filename> value in the same recipe since
1008 the resulting packages have changed. 1008 the resulting packages have changed.
1009 </para> 1009 </para>
1010 </section> 1010 </section>
@@ -1015,7 +1015,7 @@
1015 <para> 1015 <para>
1016 The license of an upstream project might change in the future. In order to prevent these changes 1016 The license of an upstream project might change in the future. In order to prevent these changes
1017 going unnoticed, the Yocto Project provides a 1017 going unnoticed, the Yocto Project provides a
1018 <glossterm><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></glossterm> 1018 <filename><link linkend='var-LIC_FILES_CHKSUM'>LIC_FILES_CHKSUM</link></filename>
1019 variable to track changes to the license text. The checksums are validated at the end of the 1019 variable to track changes to the license text. The checksums are validated at the end of the
1020 configure step, and if the checksums do not match, the build will fail. 1020 configure step, and if the checksums do not match, the build will fail.
1021 </para> 1021 </para>
@@ -1060,8 +1060,8 @@
1060 of <filename>S</filename>. 1060 of <filename>S</filename>.
1061 </para> 1061 </para>
1062 <para> 1062 <para>
1063 Note that this variable is mandatory for all recipes, unless the LICENSE variable is set to 1063 Note that this variable is mandatory for all recipes, unless the
1064 "CLOSED". 1064 <filename>LICENSE</filename> variable is set to "CLOSED".
1065 </para> 1065 </para>
1066 </section> 1066 </section>
1067 1067
@@ -1073,12 +1073,13 @@
1073 important files that contain the license text for the source code. 1073 important files that contain the license text for the source code.
1074 It is possible to specify a checksum for an entire file, or a specific section of a 1074 It is possible to specify a checksum for an entire file, or a specific section of a
1075 file (specified by beginning and ending line numbers with the "beginline" and "endline" 1075 file (specified by beginning and ending line numbers with the "beginline" and "endline"
1076 parameters respectively). The latter is useful for source files with license notice header, 1076 parameters respectively).
1077 README documents, etc. 1077 The latter is useful for source files with a license notice header,
1078 README documents, and so forth.
1078 If you do not use the "beginline" parameter, then it is assumed that the text begins on the 1079 If you do not use the "beginline" parameter, then it is assumed that the text begins on the
1079 first line of the file. 1080 first line of the file.
1080 Similarly, if you do not use the "endline" parameter, it is assumed that the license text 1081 Similarly, if you do not use the "endline" parameter, it is assumed that the license text
1081 ends as the last line of the file. 1082 ends with the last line of the file.
1082 </para> 1083 </para>
1083 1084
1084 <para> 1085 <para>