On Thu, Jul 07, 2022 at 12:07:19PM -0500, Ryan Eatmon via lists.yoctoproject.org wrote: > > > On 7/7/2022 11:19, Andrew Davis wrote: > >On 7/7/22 8:05 AM, Ryan Eatmon via lists.yoctoproject.org wrote: > >>Andrew, Denys, > >> > >>What are your thoughts on this approach to fixing the variable > >>name change issue? > >> > >> > > > >How do we feel about just using BB_PRESERVE_ENV? > > > >Andrew > > That has some potential issues with someone's environment having > something set that impacts the recipes and builds. It could make it > harder to debug issues. Right now the environment is tightly > controlled, with only variables in the list getting though, but this > just throws open the flood gates...
Ryan is correct - instructing bitbake to pass the entire environment to the build "as is" and unsanitized is quite dangerous and is not recommended. The whole point of sanitized environment is to have controlled and reproducible builds. -- Denys -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13950): https://lists.yoctoproject.org/g/meta-arago/message/13950 Mute This Topic: https://lists.yoctoproject.org/mt/92227723/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
