All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: convert unpackaged file	message from 'info' to 'warn' so that it shows up on the console
Date: Mon, 09 May 2011 08:16:20 +0100	[thread overview]
Message-ID: <4DC794C4.1090307@xora.org.uk> (raw)
In-Reply-To: <251372F6-8F97-44DF-9F1A-432B84248191@dominion.thruhere.net>

On 09/05/2011 08:11, Koen Kooi wrote:
> Op 8 mei 2011, om 08:23 heeft Khem Raj het volgende geschreven:
>
>> On 5/7/2011 9:50 AM, Darren Hart wrote:
>>> According to my discussion with RP, bb.note() is supposed to appear on
>>> the console. If it doesn't, that is a bug in bitbake, not the recipe
>> it does if we increase verbosity but it also dumps a lot of other information along. Default is to print errors and warnings which seems a sane default to me. May be there is another level which dumps notes on
>> top and then as you increase the level you get more info dumped would be
>> a good to have
> I still think that all unpackaged files are a bug, so it's more than a note anyway.
>
rpmbuild would agree with you there, so its not without precedence.

G




  reply	other threads:[~2011-05-09  7:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 14:48 [PATCH] package.bbclass: convert unpackaged file message from 'info' to 'warn' so that it shows up on the console Koen Kooi
2011-05-06 14:57 ` Mark Hatle
2011-05-06 15:19 ` Tom Rini
2011-05-07 16:50 ` Darren Hart
2011-05-08  6:23   ` Khem Raj
2011-05-09  7:11     ` Koen Kooi
2011-05-09  7:16       ` Graeme Gregory [this message]
2011-05-09  9:48   ` Richard Purdie
2011-05-09 16:06 ` Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2011-05-06 15:13 Koen Kooi
2011-05-06 16:00 ` Philip Balister
2011-05-06 16:11 ` Eric Bénard

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=4DC794C4.1090307@xora.org.uk \
    --to=dp@xora.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.