mirror of
https://git.yoctoproject.org/poky
synced 2026-04-20 18:32:12 +02:00
dev-manual, ref-manual: removed "distrodata" class
Ousted these since it was noted in the migration section that the class had been removed. Modified all references to the removed class as needed. (From yocto-docs rev: 7000acc76da6b7ee850b799347ab9083663c7e6a) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
d4fc8cf7ae
commit
f21fc9d1be
@@ -16629,16 +16629,16 @@
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
When the
|
||||
<link linkend='ref-classes-distrodata'><filename>distrodata</filename></link>
|
||||
class is enabled globally, you can perform a per-recipe
|
||||
check for what the latest upstream source code version is
|
||||
by calling
|
||||
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.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
You can use the
|
||||
<filename>UPSTREAM_CHECK_GITTAGREGEX</filename>
|
||||
variable to provide a regular expression to filter only the
|
||||
@@ -16658,11 +16658,8 @@
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
When the
|
||||
<link linkend='ref-classes-distrodata'><filename>distrodata</filename></link>
|
||||
class is enabled globally, use the
|
||||
<filename>UPSTREAM_CHECK_REGEX</filename> variable to
|
||||
specify a different regular expression instead of the
|
||||
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>.
|
||||
@@ -16680,12 +16677,9 @@
|
||||
<glossdef>
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
When the
|
||||
<link linkend='ref-classes-distrodata'><filename>distrodata</filename></link>
|
||||
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>.
|
||||
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.
|
||||
|
||||
Reference in New Issue
Block a user