helium-3rd-party/poky
1
0
Fork 0
mirror of git://git.yoctoproject.org/poky synced 2026-08-13 23:50:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

manuals: add references to the "do_fetch" task

Browse Source 
[YOCTO #14508]
(From yocto-docs rev: 17f2041647010d885f18f889c740588586c60d3a)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reported-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker 2022-09-23 17:11:53 +02:00 committed by Richard Purdie
parent 104f20717c
commit 84251f8d24
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/dev-manual/common-tasks.rst
View File

@ -9593,7 +9593,7 @@ Running Specific Tasks
----------------------
Any given recipe consists of a set of tasks. The standard BitBake
behavior in most cases is: ``do_fetch``, ``do_unpack``, ``do_patch``,
behavior in most cases is: :ref:`ref-tasks-fetch`, ``do_unpack``, ``do_patch``,
``do_configure``, ``do_compile``, ``do_install``, ``do_package``,
``do_package_write_*``, and ``do_build``. The default task is
``do_build`` and any tasks on which it depends build first. Some tasks,

2
documentation/migration-guides/migration-3.2.rst
View File

@ -191,7 +191,7 @@ Globbing no longer supported in ``file://`` entries in ``SRC_URI``
Globbing (``*`` and ``?`` wildcards) in ``file://`` URLs within :term:`SRC_URI`
did not properly support file checksums, thus changes to the source files
would not always change the do_fetch task checksum, and consequently would
would not always change the :ref:`ref-tasks-fetch` task checksum, and consequently would
not ensure that the changed files would be incorporated in subsequent builds.
Unfortunately it is not practical to make globbing work generically here, so

4
documentation/migration-guides/migration-4.0.rst
View File

@ -93,8 +93,8 @@ Fetching changes
do_mytask[network] = "1"
This is allowed by default from ``do_fetch`` but not from any of our other standard
tasks. Recipes shouldn't be accessing the network outside of ``do_fetch`` as it
This is allowed by default from :ref:`ref-tasks-fetch` but not from any of our other standard
tasks. Recipes shouldn't be accessing the network outside of :ref:`ref-tasks-fetch` as it
usually undermines fetcher source mirroring, image and licence manifests, software
auditing and supply chain security.

2
documentation/overview-manual/concepts.rst
View File

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