From: Denys Dmytriyenko <denis@denix.org>
To: reatmon@ti.com
Cc: Andrew Davis <afd@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
meta-arago@lists.yoctoproject.org
Subject: Re: [meta-arago] [oe-layersetup][master][RFC] oe-layersetup: Add config option for dunfell/kirkstone
Date: Thu, 14 Jul 2022 12:53:52 -0400 [thread overview]
Message-ID: <20220714165352.GO18692@denix.org> (raw)
In-Reply-To: <5a210eab-c490-abb5-59e2-531fcec0f8d0@ti.com>
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
next prev parent reply other threads:[~2022-07-14 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16FF8DBB7909D3F6.549@lists.yoctoproject.org>
2022-07-07 13:05 ` [meta-arago] [oe-layersetup][master][RFC] oe-layersetup: Add config option for dunfell/kirkstone Ryan Eatmon
2022-07-07 16:19 ` Andrew Davis
2022-07-07 17:07 ` Ryan Eatmon
2022-07-14 16:53 ` Denys Dmytriyenko [this message]
2022-07-07 13:03 Ryan Eatmon
2022-07-14 17:05 ` [meta-arago] " Denys Dmytriyenko
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=20220714165352.GO18692@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.