06:36 <UmbrellaMan> But isn't `${PV_pn-nano)` a global namespace variable?

06:47 <UmbrellaMan> Perhaps I didn't get some concepts clear. I get it that `PV` gets resolved to a local value for each recipe scope. But isn't there also a global list of all the `PV_pn-<recipe>` in the global scope.

07:53 <RP> UmbrellaMan: Recipes have their own individual scope and don't add data to the global scope

14:50 <u1106> UmbrellaMan: What about setting the desired nano variant in global configuration? Then the nano recipe can pick up what version to build and your image recipe can pick up the same variable and put it in the image name. (I am not an expert in the area, but I have been doing something similar for a long time, so my image name contains information about what variant has been built)

14:53 <u1106> bitbake tracks which variables are used by each recipe. So when you change the setting globablly only the 2 recipes affected will be rebuilt, the rest can be reused.

15:01 <u1106> For investigating how things work I use bitbake -e. With a recipe name it shows the variables in recipe scope. With no argument it shows global scope I have understood.

15:32 <UmbrellaMan> u1106 Thanks for the suggestion. I will end up taking that path.

18:48 <khem> RP: I have not testes Martin's patches

21:37 <RP> khem: might be worth a try with master-next of oe-core/poky