From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org, markgross@thegnar.org
Subject: Re: Tell me your build error message annoyances!
Date: Fri, 3 Jun 2011 15:48:52 +0100 [thread overview]
Message-ID: <201106031548.52577.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <20110603143545.GB27754@gvim.org>
On Friday 03 June 2011 15:35:45 mark gross wrote:
> Well perhaps it would be easier to build a list of packages that have
> been skipped? I think the cache knows about them. Perhaps they could
> be reported to a "skipped" file or something similar?
FYI there is a patch I submitted the other day to bitbake-devel which tracks
these in their own internal list. The next step is that when a NoProvider
event comes up we can look through this list to see if the requested target is
in there, and if so report that it was skipped along with the reason why. I
would think that this obviates the need to show the list of skipped packages
at the start, although we could easily allow them to be reported via some
other mechanism.
This is a separate exercise to sorting out the flow of exceptions within
bitbake, but still very important for the overall task of improving error
output.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-03 14:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 22:26 Tell me your build error message annoyances! Scott Garman
2011-06-01 1:34 ` mark gross
2011-06-01 15:06 ` Phil Blundell
2011-06-01 16:25 ` Richard Purdie
2011-06-01 16:58 ` Chris Larson
2011-06-03 14:35 ` mark gross
2011-06-03 14:48 ` Paul Eggleton [this message]
2011-06-02 14:17 ` Phil Blundell
2011-06-02 7:34 ` Martin Jansa
2011-06-03 6:10 ` Darren Hart
2011-06-03 8:11 ` Richard Purdie
2011-06-03 14:22 ` Mark Hatle
2011-06-03 15:43 ` Phil Blundell
2011-06-03 15:47 ` Chris Larson
2011-06-07 4:53 ` Darren Hart
2011-06-07 9:18 ` Richard Purdie
2011-06-06 21:13 ` Scott Garman
2011-06-03 14:57 ` Koen Kooi
2011-06-09 11:02 ` Phil Blundell
2011-06-09 11:17 ` Richard Purdie
2011-06-09 15:00 ` Scott Garman
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=201106031548.52577.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=markgross@thegnar.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