aboutsummaryrefslogtreecommitdiffstats
path: root/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
diff options
context:
space:
mode:
authorQuentin Schulz <foss@0leil.net>2021-06-01 21:22:35 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-06-06 23:17:30 +0100
commitc2c0f5126c7c784bfd7a08f127e161a58c6b5d12 (patch)
tree3c94c755be9c8051c0ff33825d19dd9a55ebdc3b /doc/bitbake-user-manual/bitbake-user-manual-execution.rst
parent376e20c1aaff197020cdb68d309b3b22f19dafe8 (diff)
downloadbitbake-c2c0f5126c7c784bfd7a08f127e161a58c6b5d12.tar.gz
doc: user-manual: ref-manual: remove mentions to BB_SETSCENE_VERIFY_FUNCTION2
This variable was removed in July 2019 with commit 5deaa5df730a "runqueue: Drop unused BB_SETSCENE_VERIFY_FUNCTION2". There's no replacement, so let's update the documentation to not mention this variable anymore. This was found by running: git grep -hoP '^ :term:`\K\w+(?=`)' doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst | \ xargs -I{} sh -c \ "grep -Rq --include='*.py' --include='*.conf' --include='*.bbclass' --include='*.bb' --include='*.bbappend' --include='*.inc' \ -w -E {}'_*(_[a-z]+[0-9a-z]*[a-z]+)*' || \ echo {}" Signed-off-by: Quentin Schulz <foss@0leil.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'doc/bitbake-user-manual/bitbake-user-manual-execution.rst')
-rw-r--r--doc/bitbake-user-manual/bitbake-user-manual-execution.rst7
1 files changed, 0 insertions, 7 deletions
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
index 14c342a6a..84d65fa9c 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
@@ -648,13 +648,6 @@ compiled binary. To handle this, BitBake calls the
each successful setscene task to know whether or not it needs to obtain
the dependencies of that task.
-Finally, after all the setscene tasks have executed, BitBake calls the
-function listed in
-:term:`BB_SETSCENE_VERIFY_FUNCTION2`
-with the list of tasks BitBake thinks has been "covered". The metadata
-can then ensure that this list is correct and can inform BitBake that it
-wants specific tasks to be run regardless of the setscene result.
-
You can find more information on setscene metadata in the
:ref:`bitbake-user-manual/bitbake-user-manual-metadata:task checksums and setscene`
section.