| Message ID | 20260501091418.76994-2-bijak.dawid@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | doc: bitbake-user-manual-metadata: clarify inherit_defer documentation | expand |
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst index 40cae6b05..ee6919dc4 100644 --- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst +++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst @@ -829,9 +829,7 @@ Here is an example:: inherit_defer ${VARNAME} -If ``VARNAME`` is -going to be set, it needs to be set before the ``inherit_defer`` statement is -parsed. One way to achieve a conditional inherit in this case is to use +One way to achieve a conditional inherit in this case is to use overrides:: VARIABLE = ""
The documentation for inherit_defer contained the claim "If VARNAME is going to be set, it needs to be set before the inherit_defer statement is parsed" which is incorrect and contradicts the purpose of inherit_defer. Drop the incorrect statement. Signed-off-by: Dawid Bijak <bijak.dawid@gmail.com> --- doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)