From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake parsing of IMAGE_INSTALL += # tslib mtd-utils" extremely user unfriendly.
Date: Tue, 21 Feb 2012 12:56:14 +0000 [thread overview]
Message-ID: <1329828974.15011.7.camel@ted> (raw)
In-Reply-To: <CAMvUbCwy5UL3YWXS=2SkeKff2WDQE9EX7-CGUv9s5SH+9uSK1g@mail.gmail.com>
On Mon, 2012-02-20 at 23:00 +0100, Leon Woestenberg wrote:
> Hello all,
>
> bitbake can really braindump on us when we insert typo's. The result
> of bitbake 1.14 parsing this one wasn't pleasant:
>
> IMAGE_INSTALL += # tslib mtd-utils"
>
> (Yes, it's a typo. No, I wouldn't expect bitbake to give me that much
> output :) )
What was the output? (I realise I can find out)
With usability issues like this, opening a bug in
bugzilla.yoctoproject.org is a good idea, particularly as we've been
focusing on cleaning up this kind of problem. Reporting them with a
known reproducible test case helps a lot as when you're looking to try
and fix these things, you need a good set of reproducers.
As a quick plug for the work that's been done already, we've now worked
through many of the issues that were reported so it is worth taking the
time to report them! :)
Cheers,
Richard
next prev parent reply other threads:[~2012-02-21 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 22:00 bitbake parsing of IMAGE_INSTALL += # tslib mtd-utils" extremely user unfriendly Leon Woestenberg
2012-02-21 12:56 ` Richard Purdie [this message]
2012-02-23 15:30 ` Eric Bénard
2012-02-23 15:32 ` Paul Eggleton
2012-02-23 15:38 ` Paul Eggleton
2012-02-23 16:06 ` Eric Bénard
2012-02-26 12:27 ` Richard Purdie
2012-02-26 13:06 ` Richard Purdie
2012-02-26 19:35 ` Leon Woestenberg
2012-02-26 23:04 ` 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=1329828974.15011.7.camel@ted \
--to=richard.purdie@linuxfoundation.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