All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] package.bbclass: convert unpackaged file message from 'info' to 'warn' so that it shows up on the console
Date: Sat, 07 May 2011 09:50:12 -0700	[thread overview]
Message-ID: <1304787012.8459.1.camel@doubt> (raw)
In-Reply-To: <1304693308-5625-1-git-send-email-koen@dominion.thruhere.net>

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
logging. I used this information to document the intended use of the
similarly named bbnote() in logging.bbclass.

--
Darren

On Fri, 2011-05-06 at 16:48 +0200, Koen Kooi wrote:
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>  meta/classes/package.bbclass |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> index e6b3df7..082f233 100644
> --- a/meta/classes/package.bbclass
> +++ b/meta/classes/package.bbclass
> @@ -676,9 +676,9 @@ python populate_packages () {
>  				unshipped.append(path)
>  
>  	if unshipped != []:
> -		bb.note("the following files were installed but not shipped in any package:")
> +		bb.warn("the following files were installed but not shipped in any package:")
>  		for f in unshipped:
> -			bb.note("  " + f)
> +			bb.warn("  " + f)
>  
>  	bb.build.exec_func("package_name_hook", d)
>  

-- 
Darren Hart
Yocto Linux Kernel




  parent reply	other threads:[~2011-05-07 16:52 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 [this message]
2011-05-08  6:23   ` Khem Raj
2011-05-09  7:11     ` Koen Kooi
2011-05-09  7:16       ` Graeme Gregory
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=1304787012.8459.1.camel@doubt \
    --to=dvhart@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 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.