Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: what is "packagegroup-core-nfs-server"?
Date: Wed, 28 Nov 2012 14:08:56 +0000	[thread overview]
Message-ID: <2817873.ANYiItS1vX@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1211280849310.26034@oneiric>

On Wednesday 28 November 2012 08:55:59 Robert P. J. Day wrote:
>   and to finalize the confusion, there's this from
> meta/classes/image.bbclass:
> 
> # IMAGE_FEATURES may contain any available package group
> 
> which would appear to be untrue at this point.  

I'm pretty sure this has never been true. We should just remove that comment.

> i think a better way to approach this would be to discuss the possible types
> of entries you might find in IMAGE_FEATURES, which appear to be:
> 
> * actual package groups
> * individual recipes(?)

I don't think this is the way to explain it. They can be values defined as 
PACKAGE_GROUP_valuename (in which you can specify one or more packages to be 
installed when the feature is enabled - where the packages could be any kind 
of runtime package including packagegroups). The term "recipe" should be 
avoided here.

> * values processed totally independently by other recipes that are
> neither package groups nor recipes (eg, "read-only-rootfs")

True. FWIW, this aspect is along the same lines as how DISTRO_FEATURES, 
MACHINE_FEATURES etc. are handled - we check for values contained in them in 
the places in the metadata where we need to be conditional upon those values.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-11-28 14:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  4:18 what is "packagegroup-core-nfs-server"? Robert P. J. Day
2012-11-28  4:27 ` Saul Wold
2012-11-28  6:18   ` Robert P. J. Day
2012-11-28 12:58   ` Robert P. J. Day
2012-11-28 13:01     ` Martin Jansa
2012-11-28 13:14       ` Robert P. J. Day
2012-11-28 13:37         ` Paul Eggleton
2012-11-28 13:45           ` Robert P. J. Day
2012-11-28 14:02             ` Paul Eggleton
2012-11-28 13:55           ` Robert P. J. Day
2012-11-28 14:08             ` Paul Eggleton [this message]

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=2817873.ANYiItS1vX@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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