manuals: add references to the "do_unpack" task

[YOCTO #14508]
Reported-by: Quentin Schulz <foss@0leil.net>
(From yocto-docs rev: 1ca57f8ec322d5777bf31829e659d62e82986be1)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker 2022-09-23 19:19:15 +02:00 committed by Richard Purdie
parent a8b6712dfd
commit c9c7ace795
4 changed files with 4 additions and 4 deletions

View File

@ -9593,7 +9593,7 @@ Running Specific Tasks
---------------------- ----------------------
Any given recipe consists of a set of tasks. The standard BitBake Any given recipe consists of a set of tasks. The standard BitBake
behavior in most cases is: :ref:`ref-tasks-fetch`, ``do_unpack``, :ref:`ref-tasks-patch`, behavior in most cases is: :ref:`ref-tasks-fetch`, :ref:`ref-tasks-unpack`, :ref:`ref-tasks-patch`,
:ref:`ref-tasks-configure`, :ref:`ref-tasks-compile`, :ref:`ref-tasks-install`, :ref:`ref-tasks-package`, :ref:`ref-tasks-configure`, :ref:`ref-tasks-compile`, :ref:`ref-tasks-install`, :ref:`ref-tasks-package`,
:ref:`do_package_write_* <ref-tasks-package_write_deb>`, and :ref:`ref-tasks-build`. The default task is :ref:`do_package_write_* <ref-tasks-package_write_deb>`, and :ref:`ref-tasks-build`. The default task is
:ref:`ref-tasks-build` and any tasks on which it depends build first. Some tasks, :ref:`ref-tasks-build` and any tasks on which it depends build first. Some tasks,

View File

@ -62,7 +62,7 @@ Previously, an inconsistent mix of spaces and tabs existed, which made
extending these functions using ``_append`` or ``_prepend`` complicated extending these functions using ``_append`` or ``_prepend`` complicated
given that Python treats whitespace as syntactically significant. If you given that Python treats whitespace as syntactically significant. If you
are defining or extending any Python functions (e.g. are defining or extending any Python functions (e.g.
``populate_packages``, ``do_unpack``, :ref:`ref-tasks-patch` and so forth) in ``populate_packages``, :ref:`ref-tasks-unpack`, :ref:`ref-tasks-patch` and so forth) in
custom recipes or classes, you need to ensure you are using consistent custom recipes or classes, you need to ensure you are using consistent
four-space indentation. four-space indentation.

View File

@ -1208,7 +1208,7 @@ end result.
The build system has knowledge of the relationship between these tasks The build system has knowledge of the relationship between these tasks
and other preceding tasks. For example, if BitBake runs and other preceding tasks. For example, if BitBake runs
``do_populate_sysroot_setscene`` for something, it does not make sense ``do_populate_sysroot_setscene`` for something, it does not make sense
to run any of the :ref:`ref-tasks-fetch`, ``do_unpack``, :ref:`ref-tasks-patch`, to run any of the :ref:`ref-tasks-fetch`, :ref:`ref-tasks-unpack`, :ref:`ref-tasks-patch`,
:ref:`ref-tasks-configure`, :ref:`ref-tasks-compile`, and :ref:`ref-tasks-install` tasks. However, if :ref:`ref-tasks-configure`, :ref:`ref-tasks-compile`, and :ref:`ref-tasks-install` tasks. However, if
:ref:`ref-tasks-package` needs to be run, BitBake needs to run those other tasks. :ref:`ref-tasks-package` needs to be run, BitBake needs to run those other tasks.

View File

@ -447,7 +447,7 @@ Validates the :term:`SRC_URI` value.
------------ ------------
Removes all output files for a target from the Removes all output files for a target from the
:ref:`ref-tasks-unpack` task forward (i.e. ``do_unpack``, :ref:`ref-tasks-unpack` task forward (i.e. :ref:`ref-tasks-unpack`,
:ref:`ref-tasks-configure`, :ref:`ref-tasks-configure`,
:ref:`ref-tasks-compile`, :ref:`ref-tasks-compile`,
:ref:`ref-tasks-install`, and :ref:`ref-tasks-install`, and