From 52e13fb0079e72cb88ec02f7af59af7f0d5ef6f7 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 30 Jun 2016 13:04:02 -0700 Subject: ref-manual: Review edits to the PR variable in glossary. Fixes [YOCTO #9843] Some minor rewordings and removal of a stray comma. (From yocto-docs rev: 9983619766bdb9d1a50948e219617aeef3170524) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 1b1c055d58..fc36af4adf 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -9598,15 +9598,17 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" 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. + A component having many packages with the same + PV usually means that the packages all + install the same upstream version, but with later + (PR) version packages including + 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 + Because manually managing PR can be cumbersome and error-prone, an automated solution exists. See the "Working With a PR Service" -- cgit v1.2.3-54-g00ecf