From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image.bbclass: fix rootfs generation without package management tools
Date: Tue, 13 Mar 2012 08:54:35 -0700 [thread overview]
Message-ID: <4F5F6DBB.6060401@linux.intel.com> (raw)
In-Reply-To: <57c7884c358bda5259c0cef0ec6fb10bc47eb158.1330749589.git.otavio@ossystems.com.br>
On 03/02/2012 08:40 PM, Otavio Salvador wrote:
> When building without package management tools the
> ROOTFS_BOOTSTRAP_INSTALL packages need to be available to provide the
> bare minimal for rootfs unconfigure postinsts to be on first boot.
>
> Those packages where being include in core-image.bbclass' based images
> however every image needs those available for proper rootfs generation.
>
> Signed-off-by: Otavio Salvador<otavio@ossystems.com.br>
> ---
> meta/classes/core-image.bbclass | 2 --
> meta/classes/image.bbclass | 7 +++++--
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/meta/classes/core-image.bbclass b/meta/classes/core-image.bbclass
> index 668297b..e2ad0fc 100644
> --- a/meta/classes/core-image.bbclass
> +++ b/meta/classes/core-image.bbclass
> @@ -51,8 +51,6 @@ CORE_IMAGE_BASE_INSTALL = '\
> task-core-boot \
> task-base-extended \
> \
> - ${@base_contains("IMAGE_FEATURES", "package-management", "", "${ROOTFS_PKGMANAGE_BOOTSTRAP}",d)} \
> - \
> ${CORE_IMAGE_EXTRA_INSTALL} \
> '
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index dfce381..8e9da99 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -5,7 +5,7 @@ inherit imagetest-${IMAGETEST}
>
> LICENSE = "MIT"
> PACKAGES = ""
> -RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL} ${NORMAL_FEATURE_INSTALL}"
> +RDEPENDS += "${IMAGE_INSTALL} ${LINGUAS_INSTALL} ${NORMAL_FEATURE_INSTALL} ${ROOTFS_BOOTSTRAP_INSTALL}"
> RRECOMMENDS += "${NORMAL_FEATURE_INSTALL_OPTIONAL}"
>
> INHIBIT_DEFAULT_DEPS = "1"
> @@ -14,6 +14,9 @@ INHIBIT_DEFAULT_DEPS = "1"
> IMAGE_FEATURES ?= ""
> IMAGE_FEATURES[type] = "list"
>
> +# rootfs bootstrap install
> +ROOTFS_BOOTSTRAP_INSTALL = "${@base_contains("IMAGE_FEATURES", "package-management", "", "${ROOTFS_PKGMANAGE_BOOTSTRAP}",d)}"
> +
> # packages to install from features
> FEATURE_INSTALL = "${@' '.join(oe.packagegroup.required_packages(oe.data.typed_value('IMAGE_FEATURES', d), d))}"
> FEATURE_INSTALL_OPTIONAL = "${@' '.join(oe.packagegroup.optional_packages(oe.data.typed_value('IMAGE_FEATURES', d), d))}"
> @@ -52,7 +55,7 @@ PACKAGE_GROUP_doc-pkgs[optional] = "1"
> IMAGE_INSTALL ?= ""
> IMAGE_INSTALL[type] = "list"
> IMAGE_BASENAME[export] = "1"
> -export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${FEATURE_INSTALL}"
> +export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${ROOTFS_BOOTSTRAP_INSTALL} ${FEATURE_INSTALL}"
> PACKAGE_INSTALL_ATTEMPTONLY ?= "${FEATURE_INSTALL_OPTIONAL}"
>
> # Images are generally built explicitly, do not need to be part of world.
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-03-13 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1330749589.git.otavio@ossystems.com.br>
2012-03-03 4:40 ` [PATCH 1/1] image.bbclass: fix rootfs generation without package management tools Otavio Salvador
2012-03-13 15:54 ` Saul Wold [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=4F5F6DBB.6060401@linux.intel.com \
--to=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox