From: Peter Seebach <peter.seebach@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] sanity.bbclass: Don't fatal() when trying to dump environment.
Date: Wed, 20 Nov 2013 09:16:59 -0600 [thread overview]
Message-ID: <20131120091659.34c6b63c@e6410-2> (raw)
In-Reply-To: <1384942744.16887.40.camel@ted>
On Wed, 20 Nov 2013 10:19:04 +0000
Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> This is creative but you just disabled the sanity tests in the graphical
> UIs like hob.
>
> isTracking() does not mean -e is being used, we use the tracking in
> other places now too.
Drat.
Perhaps an alternative would be to have -e set a specific variable, like
BB_SHOW_ENV_ONLY?
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2013-11-20 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 0:31 [PATCH 0/1] Make sanity check failures nonfatal for bitbake -e Peter Seebach
2013-11-20 0:31 ` [PATCH 1/1] sanity.bbclass: Don't fatal() when trying to dump environment Peter Seebach
2013-11-20 0:35 ` Martin Jansa
2013-11-20 0:42 ` Peter Seebach
2013-11-20 10:19 ` Richard Purdie
2013-11-20 15:16 ` Peter Seebach [this message]
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=20131120091659.34c6b63c@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox