Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Cc: Chris Larson <clarson@kergoth.com>
Subject: Re: [PATCH 1/2] classes/image: show an error on invalid IMAGE_FEATURES
Date: Fri, 10 May 2013 15:19:48 +0100	[thread overview]
Message-ID: <3510834.JaFUepN7Uz@helios> (raw)
In-Reply-To: <CABcZAN=Hs5B5Eq8iJs=+caTFBV+xLwQbjdo+2tp68MKTS5qqvw@mail.gmail.com>

On Thursday 09 May 2013 15:49:18 Chris Larson wrote:
> On Thu, May 9, 2013 at 9:24 AM, Paul Eggleton <paul.eggleton@linux.intel.com
> > wrote:
> > 
> > If the user specifies an invalid feature in IMAGE_FEATURES, show an
> > error during parsing. Valid IMAGE_FEATURES are drawn from
> > PACKAGE_GROUP_ definitions, COMPLEMENTARY_GLOBS and a new 'validitems'
> > varflag on IMAGE_FEATURES (so that additional non-package group features
> > can be added elsewhere.)
> > 
> > Implements [YOCTO #3308].
> > 
> > Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> 
> Hmm, maybe we should add this sort of valid item in a list checking to
> typecheck.bbclass, or enhance the list type in oe.types to do it there, so
> we'd have a general mechanism for this.

Good idea, I'll look into this.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-05-10 14:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09 16:24 [PATCH 0/2] Validate IMAGE_FEATURES Paul Eggleton
2013-05-09 16:24 ` [PATCH 1/2] classes/image: show an error on invalid IMAGE_FEATURES Paul Eggleton
2013-05-09 22:49   ` Chris Larson
2013-05-10 14:19     ` Paul Eggleton [this message]
2013-05-09 16:24 ` [PATCH 2/2] classes/core-image: drop apps-console-core IMAGE_FEATURES support Paul Eggleton

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=3510834.JaFUepN7Uz@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=clarson@kergoth.com \
    --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