All of lore.kernel.org
 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:02:34 +0000	[thread overview]
Message-ID: <2455772.UuKjZbS977@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1211280839110.1431@oneiric>

On Wednesday 28 November 2012 08:45:15 Robert P. J. Day wrote:
> On Wed, 28 Nov 2012, Paul Eggleton wrote:
> 
> ... snip for brevity...
> 
> > So the bit that might be missing here is that the PACKAGE_GROUP
> > structure and the packagegroup recipes/class are actually not really
> > related, except that the latter may be used to populate the former.
> > "packagegroup" is the new name for what used to be known as a "task"
> > in versions before danny and much better reflects what these recipes
> > do. 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.
> > 
> > In any case, I would definitely recommend using the term "package
> > group" to refer to packagegroup recipes only, otherwise you're only
> > likely to increase people's level of confusion.
> 
>   one more observation just to mess things up a bit more -- the fact
> that, despite what one reads in core-image.bbclass, the IMAGE_FEATURES
> variable can be used to customize your image in ways that have nothing
> to do with packages or package groups.
> 
>   witness this from meta/classes/rootfs_ipk.bbclass:
> 
>         if ${@base_contains("IMAGE_FEATURES", "read-only-rootfs", "true",
> "false" ,d)}; then if grep Status:.install.ok.unpacked ${STATUS}; then echo
> "Some packages could not be configured offline and rootfs is read-only."
> exit 1
>                 fi
>         fi
> 
> so there's a potential "image feature" called "read-only-rootfs" which
> is clearly not a package group or a package, and of which there is no
> mention in core-image.bbclass.

Yep, that's intended - there are a number of these. IMAGE_FEATURES controls 
features in the image, whether they are sets of packages to be installed or 
other aspects to enable during image construction.

This particular IMAGE_FEATURES item (read-only-rootfs) is not listed probably 
because it's limited to the ipk backend only and not widely used. There is a 
bug open to implement it for rpm and deb, at which time it should probably be 
added to the list there and to the one in the manual.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-11-28 14:16 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 [this message]
2012-11-28 13:55           ` Robert P. J. Day
2012-11-28 14:08             ` 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=2455772.UuKjZbS977@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 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.