Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] eglibc-locale: fix localedef packaging
Date: Thu, 30 Jun 2011 15:54:55 +0100	[thread overview]
Message-ID: <1309445695.20015.445.camel@rex> (raw)
In-Reply-To: <1309439074.2551.135.camel@phil-desktop>

On Thu, 2011-06-30 at 14:04 +0100, Phil Blundell wrote:
> On Thu, 2011-06-30 at 13:24 +0200, Koen Kooi wrote:
> > Does it whitelist recipes that inherit task.bbclass? I have tasks used for beagleboard workshops that drag in the native toolchain and headers for the things we need to build against (e.g. opencv, qt).
> 
> No.  The existing logic for -dbg packages, which I just reused for this
> case, does:
> 
>     if not "-dbg" in pkg and not "task-" in pkg and not "-image" in pkg:
> 
> but it doesn't have a check for inheritance as such.  If you can suggest
> a good way to identify recipes that have inherited task then I'd be
> happy to adjust the patch accordingly.

Would bb.data.inherits_class('task', d) help?

Cheers,

Richard




  parent reply	other threads:[~2011-06-30 14:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 15:30 [PATCH] eglibc-locale: fix localedef packaging Koen Kooi
2011-06-28 16:11 ` Richard Purdie
2011-06-28 20:32   ` Koen Kooi
2011-06-29 13:36     ` Phil Blundell
2011-06-29 13:49       ` Richard Purdie
2011-06-30 11:17         ` Phil Blundell
2011-06-30 11:24           ` Koen Kooi
2011-06-30 13:04             ` Phil Blundell
2011-06-30 13:40               ` Koen Kooi
2011-06-30 14:54               ` Richard Purdie [this message]
2011-06-30 14:54           ` Richard Purdie
2011-06-30 15:53             ` Saul Wold
2011-07-05 13:05           ` Richard Purdie
2011-06-29 22:31   ` Koen Kooi

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=1309445695.20015.445.camel@rex \
    --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