From f07fedb2fb12184e0b1bdf18d2924433b2ae0d02 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 8 Jun 2016 10:53:31 -0700 Subject: ref-manual: Updated the UPSTREAM_CHECK_* variables. Fixes [YOCTO #9671] (From yocto-docs rev: 8bd3f4d487bdc2929a42563eb376dc28fc33358b) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) (limited to 'documentation') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index 68ac032949..2d16019caa 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -14321,9 +14321,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" When the distrodata - class is enabled globally, you can perform a check for - what the latest upstream version is by calling - bitbake -c checkpkg. + class is enabled globally, you can perform a per-recipe + check for what the latest upstream source code version is + by calling + bitbake -c checkpkg recipe. If the recipe source code is provided from Git repositories, the OpenEmbedded build system determines the latest upstream version by picking the latest tag from the @@ -14371,9 +14372,10 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" When the distrodata - class is enabled globally, you can perform a check for what - the latest upstream version is by calling - bitbake -c checkpkg. + class is enabled globally, you can perform a per-recipe + check for what the latest upstream source code version is + by calling bitbake -c checkpkg + recipe. If the source code is provided from tarballs, the latest version is determined by fetching the directory listing where the tarball is and attempting to find a later tarball. -- cgit v1.2.3-54-g00ecf