summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-variables.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-03-28 10:20:23 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-04 14:13:39 +0100
commitfc6fffe7bfc72532d6fd8720bf68e7b6371a4ceb (patch)
tree22647fb7ea862ed14bb8318b06d17c3772f5da33 /documentation/ref-manual/ref-variables.xml
parent6317dbaa96a793bf6985713a601a2ffd85d184fe (diff)
downloadpoky-fc6fffe7bfc72532d6fd8720bf68e7b6371a4ceb.tar.gz
ref-manual: Edits to INC_PR variable.
(From yocto-docs rev: 26978211dd3dbd918cacbee1b3d1b69719832b7b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-variables.xml')
-rw-r--r--documentation/ref-manual/ref-variables.xml7
1 files changed, 4 insertions, 3 deletions
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 7f850ca941..0265bdffb5 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -1384,13 +1384,14 @@ Core layer for images cannot be removed
1384 <para>Suppose, for example, you have a set of recipes that 1384 <para>Suppose, for example, you have a set of recipes that
1385 are used across several projects. 1385 are used across several projects.
1386 And, within each of those recipes the revision 1386 And, within each of those recipes the revision
1387 (its <filename>PR</filename> value) is set accordingly. 1387 (its <link linkend='var-PR'><filename>PR</filename></link>
1388 In this case, when the revision of those recipes changes 1388 value) is set accordingly.
1389 In this case, when the revision of those recipes changes,
1389 the burden is on you to find all those recipes and 1390 the burden is on you to find all those recipes and
1390 be sure that they get changed to reflect the updated 1391 be sure that they get changed to reflect the updated
1391 version of the recipe. 1392 version of the recipe.
1392 In this scenario, it can get complicated when recipes 1393 In this scenario, it can get complicated when recipes
1393 used in many places and that provide common functionality 1394 that are used in many places and provide common functionality
1394 are upgraded to a new revision.</para> 1395 are upgraded to a new revision.</para>
1395 <para>A more efficient way of dealing with this situation is 1396 <para>A more efficient way of dealing with this situation is
1396 to set the <filename>INC_PR</filename> variable inside 1397 to set the <filename>INC_PR</filename> variable inside