From 9fece9c36125aeec1ee3b3845fc914ec0dbf3034 Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Fri, 23 Sep 2022 17:20:26 +0200 Subject: manuals: add reference to the "do_install" task [YOCTO #14508] (From yocto-docs rev: 933ad27b81dfc4a28e7c48ca7bb2d1363e8c037f) Signed-off-by: Michael Opdenacker Reported-by: Quentin Schulz Signed-off-by: Richard Purdie --- documentation/overview-manual/concepts.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'documentation/overview-manual') diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst index fa060ce0de..2e1aa3df48 100644 --- a/documentation/overview-manual/concepts.rst +++ b/documentation/overview-manual/concepts.rst @@ -1209,7 +1209,7 @@ 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 :ref:`ref-tasks-fetch`, ``do_unpack``, ``do_patch``, -``do_configure``, ``do_compile``, and ``do_install`` tasks. However, if +``do_configure``, ``do_compile``, and :ref:`ref-tasks-install` tasks. However, if ``do_package`` needs to be run, BitBake needs to run those other tasks. It becomes more complicated if everything can come from an sstate cache @@ -2163,7 +2163,7 @@ operations that are normally reserved for the root user (e.g. :ref:`do_package_write* `, :ref:`ref-tasks-rootfs`, and :ref:`do_image* `). For example, -the ``do_install`` task benefits from being able to set the UID and GID +the :ref:`ref-tasks-install` task benefits from being able to set the UID and GID of installed files to arbitrary values. One approach to allowing tasks to perform root-only operations would be -- cgit v1.2.3-54-g00ecf