mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-01-29 21:08:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

ref-manual: remove checkpkg task

Browse Source 
It doesn't exist any more and its functionality is now taken care
of by "devtool check-upgrade-status"

(From yocto-docs rev: 9c155e91dc57cb49b97805805e802330188a2c04)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2021-09-15 11:02:09 +02:00
committed by Richard Purdie
parent d6966a39f2
commit b931182b5b
2 changed files with 2 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
documentation/ref-manual/tasks.rst
View File

@@ -438,37 +438,6 @@ Manually Called Tasks
These tasks are typically manually triggered (e.g. by using the
``bitbake -c`` command-line option):
.. _ref-tasks-checkpkg:
``do_checkpkg``
---------------
Provides information about the recipe including its upstream version and
status. The upstream version and status reveals whether or not a version
of the recipe exists upstream and a status of not updated, updated, or
unknown.
To check the upstream version and status of a recipe, use the following
devtool commands::
$ devtool latest-version
$ devtool check-upgrade-status
See the ":ref:`ref-manual/devtool-reference:\`\`devtool\`\` quick reference`"
chapter for more information on
``devtool``. See the ":ref:`devtool-checking-on-the-upgrade-status-of-a-recipe`"
section for information on checking the upgrade status of a recipe.
To build the ``checkpkg`` task, use the ``bitbake`` command with the
"-c" option and task name::
$ bitbake core-image-minimal -c checkpkg
By default, the results are stored in :term:`$LOG_DIR <LOG_DIR>` (e.g.
``$BUILD_DIR/tmp/log``).
.. _ref-tasks-checkuri:
``do_checkuri``
---------------

4
documentation/ref-manual/variables.rst
View File

@@ -8497,7 +8497,7 @@ system and gives an overview of their function and contents.
:term:`UPSTREAM_CHECK_GITTAGREGEX`
You can perform a per-recipe check for what the latest upstream
source code version is by calling ``bitbake -c checkpkg`` recipe. If
source code version is by calling ``devtool latest-version 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 list of all repository tags.
@@ -8520,7 +8520,7 @@ system and gives an overview of their function and contents.
:term:`UPSTREAM_CHECK_URI`
You can perform a per-recipe check for what the latest upstream
source code version is by calling ``bitbake -c checkpkg`` recipe. If
source code version is by calling ``devtool latest-version 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. When this approach does not work,