From cf181cdb52f8f51f789da596a5577b508227dbac Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 29 Jun 2016 08:32:49 -0700 Subject: ref-manual: Updated the PR variable description. Fixes [YOCTO #9843] The variable description was very brief. These changes added some substance to the description and how the OpenEmbedded build system uses the variable. (From yocto-docs rev: 7603eee7f3d31edaf5a01d3e0deedb8dc53a66b4) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 42 ++++++++++++++++++++++++++++-- 1 file changed, 40 insertions(+), 2 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 433893b93d..ed735a7eb3 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -9571,8 +9571,46 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" - The revision of the recipe. - The default value for this variable is "r0". + The revision of the recipe. The default value for this + variable is "r0". + Subsequent revisions of the recipe conventionally have the + values "r1", "r2", and so forth. + When + PV + increases, PR is conventionally reset + to "r0". + + The OpenEmbedded build system does not need the aid of + PR to know when to rebuild a + recipe. + The build system uses + STAMP + and the + shared state cache + mechanisms. + + The PR variable primarily becomes + significant when a package manager dynamically installs + packages on an already built image. + In this case, PR, which is the default + value of + PKGR, + helps the package manager distinguish which package is the + most recent one in cases where many packages have the same + PV (i.e. PKGV). + Packages have the same PV usually + when the package manager installs the same upstream version + and some of the packages include packaging fixes. + + PR does not need to be increased + for changes that do not change the package contents or + metadata. + + Because, manually managing PR can be + cumbersome and error-prone, an automated solution exists. + See the + "Working With a PR Service" + section for more information. -- cgit v1.2.3-54-g00ecf