aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-variables.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/ref-variables.xml')
-rw-r--r--documentation/ref-manual/ref-variables.xml44
1 files changed, 25 insertions, 19 deletions
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index d5ff132e43..2d16019caa 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -14319,15 +14319,18 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<glossdef>
<para role="glossdeffirst">
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
- For recipes that use the
+ When the
<link linkend='ref-classes-distrodata'><filename>distrodata</filename></link>
- class, this variable causes the OpenEmbedded build system
- to check for what the latest upstream version is by calling
- <filename>bitbake -c checkpkg</filename>.
- When source code is provided from Git repositories, the
- latest upstream version is determined by picking the latest
- tag from the list of all repository tags.
- You can use the <filename>UPSTREAM_CHECK_GITTAGREGEX</filename>
+ class is enabled globally, you can perform a per-recipe
+ check for what the latest upstream source code version is
+ by calling
+ <filename>bitbake -c checkpkg</filename> <replaceable>recipe</replaceable>.
+ 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
+ list of all repository tags.
+ You can use the
+ <filename>UPSTREAM_CHECK_GITTAGREGEX</filename>
variable to provide a regular expression to filter only the
relevant tags should the default filter not work
correctly.
@@ -14345,11 +14348,13 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<glossdef>
<para role="glossdeffirst">
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
- For recipes that use the
+ When the
<link linkend='ref-classes-distrodata'><filename>distrodata</filename></link>
- class, the <filename>UPSTREAM_CHECK_REGEX</filename>
- variable causes the package checking system to use the
- regular expression to parse the page found using
+ class is enabled globally, use the
+ <filename>UPSTREAM_CHECK_REGEX</filename> variable to
+ specify a different regular expression instead of the
+ default one when the package checking system is parsing
+ the page found using
<link linkend='var-UPSTREAM_CHECK_URI'><filename>UPSTREAM_CHECK_URI</filename></link>.
<literallayout class='monospaced'>
UPSTREAM_CHECK_REGEX = "package_regex"
@@ -14365,16 +14370,17 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<glossdef>
<para role="glossdeffirst">
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
- For recipes that use the
+ When the
<link linkend='ref-classes-distrodata'><filename>distrodata</filename></link>
- class, this variable causes the OpenEmbedded build system
- to check for what the latest upstream version is by calling
- <filename>bitbake -c checkpkg</filename>.
- When the source code is provided from tarballs, the latest
+ class is enabled globally, you can perform a per-recipe
+ check for what the latest upstream source code version is
+ by calling <filename>bitbake -c checkpkg</filename>
+ <replaceable>recipe</replaceable>.
+ 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.
- When this approach does not work,
- you can use <filename>UPSTREAM_CHECK_URI</filename> to
+ When this approach does not work, you can use
+ <filename>UPSTREAM_CHECK_URI</filename> to
provide a different URI that contains the link to the
latest tarball.
<literallayout class='monospaced'>