From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Chris Larson <chris_larson@mentor.com>
Subject: Re: [PATCH 4/5] image.bbclass: switch to OE's IMAGE_FEATURES
Date: Fri, 20 May 2011 19:05:53 +0100 [thread overview]
Message-ID: <1305914753.3424.670.camel@rex> (raw)
In-Reply-To: <b7564c32452e9ce33d9790465b986471ef5a3cba.1305752660.git.chris_larson@mentor.com>
On Wed, 2011-05-18 at 14:06 -0700, Chris Larson wrote:
> From: Chris Larson <chris_larson@mentor.com>
>
> Currently, all image features are assumed to be package groups defined with
> oe.packagegroup (PACKAGE_GROUP_<group> = "<list of packages>").
>
> Signed-off-by: Chris Larson <chris_larson@mentor.com>
> ---
> meta/classes/core-image.bbclass | 112 ++++++++++++++-------------------------
> meta/classes/image.bbclass | 41 ++++++++++++++-
> meta/conf/bitbake.conf | 1 +
> 3 files changed, 79 insertions(+), 75 deletions(-)
> - SDK
> @@ -26,75 +24,43 @@ LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3
> # - nfs-server - NFS server (exports / over NFS to everybody)
> # - ssh-server-dropbear - SSH server (dropbear)
> # - ssh-server-openssh - SSH server (openssh)
> -# - dev-pkgs - development packages
> -# - dbg-pkgs - debug packages
> #
I like the patch, there are just two things which bother me a little.
Firstly, if I understand correctly and haven't missed anything,
"dev-pkgs" becomes "dev" with this change?
A quick grep shows users of this such as:
recipes-core/images/core-image-minimal-dev.bb:IMAGE_FEATURES += "dev-pkgs"
recipes-extended/images/core-image-lsb-sdk.bb:IMAGE_FEATURES += "apps-console-core tools-debug tools-profile tools-sdk dev-pkgs ssh-server-openssh"
recipes-extended/images/core-image-lsb-dev.bb:IMAGE_FEATURES += "apps-console-core dev-pkgs ssh-server-openssh"
recipes-sato/images/core-image-sato-dev.bb:IMAGE_FEATURES += "apps-console-core ${SATO_IMAGE_FEATURES} dev-pkgs"
recipes-sato/images/core-image-sato-sdk.bb:IMAGE_FEATURES += "apps-console-core ${SATO_IMAGE_FEATURES} tools-debug tools-profile tools-sdk dev-pkgs qt4-pkgs"
and I'd expect the changelog to at least mention it and correct this.
I'm also thinking IMAGE_FEATURES = "dev" doesn't really indicate what it
means very clearly which is why dev-pkgs was originally used...
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -11,8 +11,45 @@ INHIBIT_DEFAULT_DEPS = "1"
>
> # "export IMAGE_BASENAME" not supported at this time
> IMAGE_BASENAME[export] = "1"
> -export PACKAGE_INSTALL ?= "${IMAGE_INSTALL}"
> -PACKAGE_INSTALL_ATTEMPTONLY ?= ""
> +
> +PACKAGE_INSTALL = "${@' '.join(oe.packagegroup.required_packages('${IMAGE_FEATURES}'.split(), d))}"
> +PACKAGE_INSTALL_ATTEMPTONLY = "${@' '.join(oe.packagegroup.optional_packages('${IMAGE_FEATURES}'.split(), d))}"
> +RDEPENDS += "${@' '.join(oe.packagegroup.active_packages('${IMAGE_FEATURES}'.split(), d))}"
I also noticed this patch changes things so PACKAGE_INSTALL_ATTEMPTONLY
is used for the dev/doc/dbg packages. I'm not sure its a major issue but
it is a change in behaviour and I'd have expected it in the commit
message.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-20 18:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 21:06 [PATCH 0/5] Switch to OE's implementation of IMAGE_FEATURES Chris Larson
2011-05-18 21:06 ` [PATCH 1/5] oe.packagegroup: add code for package groups (sync from OE) Chris Larson
2011-05-18 21:06 ` [PATCH 2/5] Move packagedata code into oe.packagedata " Chris Larson
2011-05-18 21:06 ` [PATCH 3/5] packagedata: don't choke on empty PACKAGES Chris Larson
2011-05-18 21:06 ` [PATCH 4/5] image.bbclass: switch to OE's IMAGE_FEATURES Chris Larson
2011-05-20 18:05 ` Richard Purdie [this message]
2011-05-20 18:09 ` Chris Larson
2011-05-20 18:29 ` Richard Purdie
2011-05-20 18:38 ` Chris Larson
2011-05-18 21:06 ` [PATCH 5/5] Use oe.data for IMAGE_FEATURES Chris Larson
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=1305914753.3424.670.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=chris_larson@mentor.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 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.