what is "packagegroup-core-nfs-server"?

what is "packagegroup-core-nfs-server"?

[Robert P. J. Day]

  poking around core-image.bbclass, and noticed this:

PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"

except i don't see the corresponding packagegroup-core-nfs-server.bb
recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
above processed?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is "packagegroup-core-nfs-server"?

[Saul Wold]

On 11/27/2012 08:18 PM, Robert P. J. Day wrote:
>
>    poking around core-image.bbclass, and noticed this:
>
> PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"
>
> except i don't see the corresponding packagegroup-core-nfs-server.bb
> recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
> above processed?
>
It's defined in recipes-core/packagegroups/packagegroup-core-nfs.bb

The line
PACKAGES = "${PN}-server"
provides the key you are looking for.

Hope that helps.

Sau!

> rday
>

Re: what is "packagegroup-core-nfs-server"?

[Robert P. J. Day]

On Tue, 27 Nov 2012, Saul Wold wrote:

> On 11/27/2012 08:18 PM, Robert P. J. Day wrote:
> >
> >    poking around core-image.bbclass, and noticed this:
> >
> > PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"
> >
> > except i don't see the corresponding packagegroup-core-nfs-server.bb
> > recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
> > above processed?
> >
> It's defined in recipes-core/packagegroups/packagegroup-core-nfs.bb
>
> The line
> PACKAGES = "${PN}-server"
> provides the key you are looking for.

  ah, quite so, thanks.  i figured it was something obvious.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is "packagegroup-core-nfs-server"?

[Robert P. J. Day]

On Tue, 27 Nov 2012, Saul Wold wrote:

> On 11/27/2012 08:18 PM, Robert P. J. Day wrote:
> >
> >    poking around core-image.bbclass, and noticed this:
> >
> > PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"
> >
> > except i don't see the corresponding packagegroup-core-nfs-server.bb
> > recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
> > above processed?
> >
> It's defined in recipes-core/packagegroups/packagegroup-core-nfs.bb
>
> The line
> PACKAGES = "${PN}-server"
> provides the key you are looking for.

  a followup, for which i'm quite prepared to embarrass myself --
where is the "splash" package group defined?  i can see this in
image.bbclass:

SPLASH ?= "psplash"
PACKAGE_GROUP_splash = "${SPLASH}"

and numerous images add that "splash" package group.  but my first
impression was that any package would be defined under some
"packagegroups/" directory, and would necessarily need to "inherit
packagegroup".

  so what am i missing?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is "packagegroup-core-nfs-server"?

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1291 bytes --]

On Wed, Nov 28, 2012 at 07:58:45AM -0500, Robert P. J. Day wrote:
> On Tue, 27 Nov 2012, Saul Wold wrote:
> 
> > On 11/27/2012 08:18 PM, Robert P. J. Day wrote:
> > >
> > >    poking around core-image.bbclass, and noticed this:
> > >
> > > PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"
> > >
> > > except i don't see the corresponding packagegroup-core-nfs-server.bb
> > > recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
> > > above processed?
> > >
> > It's defined in recipes-core/packagegroups/packagegroup-core-nfs.bb
> >
> > The line
> > PACKAGES = "${PN}-server"
> > provides the key you are looking for.
> 
>   a followup, for which i'm quite prepared to embarrass myself --
> where is the "splash" package group defined?  i can see this in
> image.bbclass:
> 
> SPLASH ?= "psplash"
> PACKAGE_GROUP_splash = "${SPLASH}"
> 
> and numerous images add that "splash" package group.  but my first
> impression was that any package would be defined under some
> "packagegroups/" directory, and would necessarily need to "inherit
> packagegroup".
> 
>   so what am i missing?

PACKAGE_GROUP_foo can be provided by any recipe, not only packagegroup-*

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: what is "packagegroup-core-nfs-server"?

[Robert P. J. Day]

On Wed, 28 Nov 2012, Martin Jansa wrote:

> On Wed, Nov 28, 2012 at 07:58:45AM -0500, Robert P. J. Day wrote:
> > On Tue, 27 Nov 2012, Saul Wold wrote:
> >
> > > On 11/27/2012 08:18 PM, Robert P. J. Day wrote:
> > > >
> > > >    poking around core-image.bbclass, and noticed this:
> > > >
> > > > PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"
> > > >
> > > > except i don't see the corresponding packagegroup-core-nfs-server.bb
> > > > recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
> > > > above processed?
> > > >
> > > It's defined in recipes-core/packagegroups/packagegroup-core-nfs.bb
> > >
> > > The line
> > > PACKAGES = "${PN}-server"
> > > provides the key you are looking for.
> >
> >   a followup, for which i'm quite prepared to embarrass myself --
> > where is the "splash" package group defined?  i can see this in
> > image.bbclass:
> >
> > SPLASH ?= "psplash"
> > PACKAGE_GROUP_splash = "${SPLASH}"
> >
> > and numerous images add that "splash" package group.  but my first
> > impression was that any package would be defined under some
> > "packagegroups/" directory, and would necessarily need to "inherit
> > packagegroup".
> >
> >   so what am i missing?
>
> PACKAGE_GROUP_foo can be provided by any recipe, not only
> packagegroup-*

  ok, that's useful information that doesn't seem to be documented
anywhere (or is it?).

  however, if a regular recipe can be used as the basis for a package
group, would it not still have to contain "inherit packagegroup" to be
defined as a package group?  or can any regular recipe act as its own
package group?  i examined the "psplash" recipe and i saw nothing that
suggested it was available as a package group.

  i realize these are nitpicky questions but it's the sort of thing
someone's guaranteed to ask me at some point, so i want to nail it
down.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is "packagegroup-core-nfs-server"?

[Paul Eggleton]

On Wednesday 28 November 2012 08:14:44 Robert P. J. Day wrote:
> On Wed, 28 Nov 2012, Martin Jansa wrote:
> > On Wed, Nov 28, 2012 at 07:58:45AM -0500, Robert P. J. Day wrote:
> > > On Tue, 27 Nov 2012, Saul Wold wrote:
> > > > On 11/27/2012 08:18 PM, Robert P. J. Day wrote:
> > > > >    poking around core-image.bbclass, and noticed this:
> > > > > PACKAGE_GROUP_nfs-server = "packagegroup-core-nfs-server"
> > > > > 
> > > > > except i don't see the corresponding packagegroup-core-nfs-server.bb
> > > > > recipe file.  there *is* a packagegroup-core-nfs.bb file; how is the
> > > > > above processed?
> > > > 
> > > > It's defined in recipes-core/packagegroups/packagegroup-core-nfs.bb
> > > > 
> > > > The line
> > > > PACKAGES = "${PN}-server"
> > > > provides the key you are looking for.
> > > > 
> > >   a followup, for which i'm quite prepared to embarrass myself --
> > > 
> > > where is the "splash" package group defined?  i can see this in
> > > image.bbclass:
> > > 
> > > SPLASH ?= "psplash"
> > > PACKAGE_GROUP_splash = "${SPLASH}"
> > > 
> > > and numerous images add that "splash" package group.  but my first
> > > impression was that any package would be defined under some
> > > "packagegroups/" directory, and would necessarily need to "inherit
> > > packagegroup".
> > > 
> > >   so what am i missing?
> > 
> > PACKAGE_GROUP_foo can be provided by any recipe, not only
> > packagegroup-*
> 
>   ok, that's useful information that doesn't seem to be documented
> anywhere (or is it?).
> 
>   however, if a regular recipe can be used as the basis for a package
> group, would it not still have to contain "inherit packagegroup" to be
> defined as a package group?  or can any regular recipe act as its own
> package group?  i examined the "psplash" recipe and i saw nothing that
> suggested it was available as a package group.
> 
>   i realize these are nitpicky questions but it's the sort of thing
> someone's guaranteed to ask me at some point, so i want to nail it
> down.

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.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: what is "packagegroup-core-nfs-server"?

[Robert P. J. Day]

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.

  i had a nice little tutorial going for IMAGE_FEATURES, now i'm going
to have to go back and rethink it.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is "packagegroup-core-nfs-server"?

[Robert P. J. Day]

  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 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(?)
* values processed totally independently by other recipes that are
neither package groups nor recipes (eg, "read-only-rootfs")

  i can see i have my work cut out for me today. :-)

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is "packagegroup-core-nfs-server"?

[Paul Eggleton]

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

Re: what is "packagegroup-core-nfs-server"?

[Paul Eggleton]

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