diff options
| -rw-r--r-- | documentation/ref-manual/ref-variables.xml | 7 |
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 |