From: Dawid Bijak <bijak.dawid@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org, quentin.schulz@cherry.de,
richard.purdie@linuxfoundation.org,
Dawid Bijak <bijak.dawid@gmail.com>
Subject: [PATCH v3 1/3] doc: bitbake-user-manual-metadata: remove incorrect claim
Date: Sat, 9 May 2026 12:43:05 +0200 [thread overview]
Message-ID: <20260509104307.26698-2-bijak.dawid@gmail.com> (raw)
In-Reply-To: <20260509104307.26698-1-bijak.dawid@gmail.com>
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>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
---
doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
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 = ""
--
2.48.1
next prev parent reply other threads:[~2026-05-09 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 10:43 [PATCH v3 0/3] doc: bitbake-user-manual-metadata: clarify inherit_defer documentation Dawid Bijak
2026-05-09 10:43 ` Dawid Bijak [this message]
2026-05-09 10:43 ` [PATCH v3 2/3] doc: bitbake-user-manual-metadata: remove invalid anonymous Python example Dawid Bijak
2026-05-09 10:43 ` [PATCH v3 3/3] doc: bitbake-user-manual-metadata: explain inherit_defer example Dawid Bijak
2026-05-11 12:39 ` [docs] [PATCH v3 0/3] doc: bitbake-user-manual-metadata: clarify inherit_defer documentation Mathieu Dubois-Briand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260509104307.26698-2-bijak.dawid@gmail.com \
--to=bijak.dawid@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox