bitbake: 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 {}"

(Bitbake rev: c2c0f5126c7c784bfd7a08f127e161a58c6b5d12)

Signed-off-by: Quentin Schulz <foss@0leil.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Quentin Schulz
2021-06-01 21:22:35 +02:00
committed by Richard Purdie
parent 2c37ab65e5
commit c9ef89b3b9
3 changed files with 0 additions and 22 deletions

View File

@@ -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.

View File

@@ -1920,10 +1920,6 @@ The following list describes related variables:
Specifies a function BitBake calls that determines whether BitBake
requires a setscene dependency to be met.
- :term:`BB_SETSCENE_VERIFY_FUNCTION2`:
Specifies a function to call that verifies the list of planned task
execution before the main task execution happens.
- :term:`BB_STAMP_POLICY`: Defines the mode
for comparing timestamps of stamp files.

View File

@@ -426,17 +426,6 @@ overview of their function and contents.
The function specified by this variable returns a "True" or "False"
depending on whether the dependency needs to be met.
:term:`BB_SETSCENE_VERIFY_FUNCTION2`
Specifies a function to call that verifies the list of planned task
execution before the main task execution happens. The function is
called once BitBake has a list of setscene tasks that have run and
either succeeded or failed.
The function allows for a task list check to see if they make sense.
Even if BitBake was planning to skip a task, the returned value of
the function can force BitBake to run the task, which is necessary
under certain metadata defined circumstances.
:term:`BB_SIGNATURE_EXCLUDE_FLAGS`
Lists variable flags (varflags) that can be safely excluded from
checksum and dependency data for keys in the datastore. When