From: Phil Blundell <philb@gnu.org>
To: openembedded-core@lists.openembedded.org
Subject: overuse of bitbake flags considered harmful
Date: Thu, 27 Sep 2012 13:22:17 +0100 [thread overview]
Message-ID: <1348748538.32611.18.camel@phil-desktop> (raw)
I was mildly amused to discover, the other day, that the output of
"bitbake -e rpm | grep PACKAGECONFIG" is not quite as one might naïvely
expect.
I guess the right response to this is perhaps that bitbake ought
nowadays to find some other way to store its own internal state, since
the idiom of using flags is pretty well established in oe-core.
p.
next reply other threads:[~2012-09-27 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 12:22 Phil Blundell [this message]
2012-09-27 15:27 ` overuse of bitbake flags considered harmful Richard Purdie
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=1348748538.32611.18.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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