From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rpjday@crashcourse.ca,
YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] BB explanation of BB_ENV_PASSTHROUGH is confusing
Date: Wed, 07 Jan 2026 14:46:17 +0000 [thread overview]
Message-ID: <e88a8ee06cbb9c3f25cd7485c898308fccd4b08b.camel@linuxfoundation.org> (raw)
In-Reply-To: <5cc0f4e6-3722-74a3-cf42-4f919d1ed314@crashcourse.ca>
On Wed, 2026-01-07 at 06:39 -0800, Robert P. J. Day via lists.yoctoproject.org wrote:
>
> here:
>
> https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_ENV_PASSTHROUGH
>
> the explanation:
>
> "Specifies the internal list of variables to allow through from the
> external environment into BitBake’s datastore. If the value of this
> variable is not specified (which is the default), the following list
> is used: BBPATH, BB_PRESERVE_ENV, BB_ENV_PASSTHROUGH, and
> BB_ENV_PASSTHROUGH_ADDITIONS."
>
> seems weird since it suggests that if the value of that variable is
> not specified, the list that is used recursively *includes* the
> variable itself. and this doesn't seem to match the code from
> lib/bb/utils.py, which does *not* include that variable:
>
> def preserved_envvars():
> """Returns the list of variables which are taken from the environment and
> placed in the metadata."""
> v = [
> 'BBPATH',
> 'BB_PRESERVE_ENV',
> 'BB_ENV_PASSTHROUGH_ADDITIONS',
> ]
> return v + preserved_envvars_exported()
>
> can someone clarify how that explanation should be interpreted? or how
> it might be made clearer?
It probably needs updating after this:
https://git.openembedded.org/bitbake/commit/lib/bb/utils.py?id=0a33b560233b983456178541603ab96fea22238b
Cheers,
Richard
next prev parent reply other threads:[~2026-01-07 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:42 BB explanation of BB_ENV_PASSTHROUGH is confusing Robert P. J. Day
2026-01-07 14:46 ` Richard Purdie [this message]
2026-01-14 15:43 ` [docs] " Quentin Schulz
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=e88a8ee06cbb9c3f25cd7485c898308fccd4b08b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=docs@lists.yoctoproject.org \
--cc=rpjday@crashcourse.ca \
/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