Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	openembedded-core@lists.openembedded.org
Subject: Re: some simple questions/observations about package groups
Date: Thu, 29 Nov 2012 14:44:19 +0000	[thread overview]
Message-ID: <3409560.zPX7xbNTKL@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1211290652280.3805@oneiric>

On Thursday 29 November 2012 06:58:02 Robert P. J. Day wrote:
> On Thu, 29 Nov 2012, Paul Eggleton wrote:
> > On Wednesday 28 November 2012 15:27:58 Chris Larson wrote:
> > > Also, to comment on something tangentially related from a different
> > > thread,
> > > technically the PACKAGE_GROUP_ variables were the first to use the term
> > > as
> > > far as I'm aware. *tasks* were then renamed to use that name as well,
> > > which
> > > is where a bunch of the confusion probably got introduced.
> > 
> > I did mention that:
> > > PACKAGE_GROUP_* actually came first as a way to
> > > define items for IMAGE_FEATURES that map to one or more packages, and
> > > I'm
> > > not  sure the name choice was a particularly good one - I wonder if it
> > > would be worth considering renaming it to something like
> > > IMAGE_FEATURE_PACKAGES in order to avoid confusion, although obviously
> > > every rename like this has a cost associated.
> 
>   before i forgot all of this, i lashed together this wiki page for my
> own benefit so i'd have some examples to show students:
> 
> http://www.crashcourse.ca/wiki/index.php/OE_package_groups
> 
> it's admittedly in rough form and could use some polishing but it will
> do for now.  feedback?  errors?

You're describing those things defined by PACKAGE_GROUP_* as package groups, 
which I would strongly advise against. I know the naming of PACKAGE_GROUP_* 
suggests that the two are part of the same thing but they really aren't. Most 
of this page apart from section 5 is actually talking about IMAGE_FEATURES and 
should be reworded as such if you want to reduce confusion rather than 
increasing it.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-11-29 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28 11:45 some simple questions/observations about package groups Robert P. J. Day
2012-11-28 22:26 ` Chris Larson
2012-11-28 22:27   ` Chris Larson
2012-11-29 11:40     ` Paul Eggleton
2012-11-29 11:58       ` Robert P. J. Day
2012-11-29 14:44         ` Paul Eggleton [this message]
2012-11-29 14:46           ` Robert P. J. Day

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=3409560.zPX7xbNTKL@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