From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] insane bbclass: turn fatal errors back into fatal errors
Date: Thu, 30 Jun 2011 16:33:48 +0100 [thread overview]
Message-ID: <201106301633.48933.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1309446689-21243-1-git-send-email-koen@dominion.thruhere.net>
On Thursday 30 June 2011 16:11:29 Koen Kooi wrote:
> These were turned off by:
>
> commit fae8d5e985e9b05ce90f1eca434ad4dbf2259725
> Author: Richard Purdie <rpurdie@linux.intel.com>
> Date: Thu Jul 8 23:51:06 2010 +0100
>
> insane.bbclass: Relax fatal errors for now until we get have time to
work
> through the backlog
>
> The current metadata triggers so many of these that they need to be made
> fatal so people will actually fix them.
...
> return not error_class in [0, 5, 7, 8, 9]
So in principle I can agree that making these fatal again will make people
sort out the problems that they are flagging up. However, why is class 7 -
.desktop files being "invalid" - a fatal error, considering there are many sub-
classes of "invalidity" being tested for with varying levels of significance?
(This has probably been discussed on the OE list before but IMHO it merits
revisiting if so.)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-30 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 15:11 [PATCH] insane bbclass: turn fatal errors back into fatal errors Koen Kooi
2011-06-30 15:33 ` Paul Eggleton [this message]
2011-06-30 15:49 ` Koen Kooi
2011-06-30 15:59 ` Paul Eggleton
2011-07-01 16:25 ` Richard Purdie
2011-07-01 17:12 ` Richard Purdie
2011-07-01 17:16 ` Khem Raj
2011-07-01 17:25 ` Mark Hatle
2011-07-01 17:33 ` Koen Kooi
2011-07-01 18:18 ` Richard Purdie
2011-07-04 14:10 ` Paul Eggleton
2011-07-05 10:38 ` Richard Purdie
2011-07-01 14:55 ` Phil Blundell
2011-07-01 15:09 ` Koen Kooi
2011-06-30 15:58 ` Tom Rini
2011-06-30 16:08 ` Mark Hatle
2011-06-30 20:35 ` Koen Kooi
2011-06-30 20:59 ` 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=201106301633.48933.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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