Bug 14072

Summary:	modification to BB_BASEHASH_IGNORE_VARS from within recipe should trigger a warning
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Yann Dirson <ydirson>
Component:	bitbake	Assignee:	Unassigned <unassigned>
Status:	IN PROGRESS IMPLEMENTATION ---	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	michael.opdenacker, poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie, simone.p.weiss
Version:	unspecified
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Yann Dirson 2020-10-01 06:58:47 UTC

Appending to BB_HASHBASE_WHITELIST is reflected in "bitbake -e" output, but has no effect.  This is quite confusing.

It would be useful to warn the user that this construct will be ignored (or even error out ?), and suggest other routes, like SRC_URI[vardepsexclude] or changing BB_HASHBASE_WHITELIST at layer level (the latter the case that bit me, ie. having to export an access token through an envvar to the fetch command).

Comment 1 Richard Purdie 2020-10-01 07:49:58 UTC

The challenge here is consistency with other variables. If we do this for this variable we need to make this happen for every variable which can't be set in recipe context. I worry we need to try and be consistent. I do see the issue here with making it visible to the user why its not working though.

Comment 2 Michael Opdenacker 2022-10-06 14:50:30 UTC

Replaced BB_HASHBASE_WHITELIST by BB_BASEHASH_IGNORE_VARS in the title.
The issue remains the same.

Comment 3 Simone Weiß 2024-02-07 06:03:53 UTC

As a first step, I plan to update the variable glossary at: https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html.
At some hint if variables are global or not.

And check if changes are needed also here: https://docs.yoctoproject.org/ref-manual/varlocality.html


The other potential idea I have is to somehow annotate the output of bitbake -e with this info. An error or warning I would not add (for now?), as this would likely cause many of them...