13599 2019-10-17 15:23:14 +0000 Enhancement: Detect variables that shouldn't be defined in image scope, but in global (distro) scope 2026-10-01 15:48:12 +0000 1 1 10 QA/Testing Build Testing general unspecified x86 Multiple NEW Medium+ enhancement 6.2 1 mark.hatle richard.purdie randy.macleod --- --- Yes (doc changes required) oldest_to_newest 85378 0 mark.hatle 2019-10-17 15:23:14 +0000 I've seen numerous instances of people trying to set VIRTUAL_RUNTIME_... within an image bb or image bbappend, and then not being able to figure out why it's being "ignored". There needs to be a way to define the scope of a variable (in human, if not machine terms) and then scan for violations of the scope. One possible way to do this would be to add a (standard) 'scope' flag to variables. If unset, it's everywhere.. if it's set to 'distro', then it can only be "set" outside of a recipe. If it's set to 'recipe' it needs to be set within a recipe or using an override (such as pn-recipe)...