From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] rootfs_ipk.bbclass: fix detection of script runtime requirement
Date: Thu, 2 Feb 2012 09:48:16 +0100 [thread overview]
Message-ID: <20120202084816.GE3697@jama.jama.net> (raw)
In-Reply-To: <cc36eb9f3e699b9c4478e4de0939e50eb317446f.1328127940.git.otavio@ossystems.com.br>
[-- Attachment #1: Type: text/plain, Size: 1637 bytes --]
On Wed, Feb 01, 2012 at 08:27:45PM +0000, Otavio Salvador wrote:
> The code has been broken by 2feba313c991170747381c7cf821a45c2cd04632
> that changed the way this detection has being done.
Wasn't this fixed by
http://git.openembedded.org/openembedded-core/commit/?id=6d3eac57bdba8e2582c210a2f82a3a4546f68581
?
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta/classes/rootfs_ipk.bbclass | 10 ++++++++--
> 1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/rootfs_ipk.bbclass b/meta/classes/rootfs_ipk.bbclass
> index 48fb2fb..0881089 100644
> --- a/meta/classes/rootfs_ipk.bbclass
> +++ b/meta/classes/rootfs_ipk.bbclass
> @@ -74,9 +74,15 @@ fakeroot rootfs_ipk_do_rootfs () {
>
> ${OPKG_POSTPROCESS_COMMANDS}
> ${ROOTFS_POSTINSTALL_COMMAND}
> -
> +
> + if grep -q Status:.install.ok.unpacked ${IMAGE_ROOTFS}${opkglibdir}status; then
> + runtime_script_required=1
> + else
> + runtime_script_required=0
> + fi
> +
> if ${@base_contains("IMAGE_FEATURES", "read-only-rootfs", "true", "false" ,d)}; then
> - if grep Status:.install.ok.unpacked ${IMAGE_ROOTFS}${opkglibdir}status; then
> + if [ $runtime_script_required -eq 1 ]; then
> echo "Some packages could not be configured offline and rootfs is read-only."
> exit 1
> fi
> --
> 1.7.2.5
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-02-02 8:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 20:27 [PATCH 0/3] Pending patches in O.S. Systems tree Otavio Salvador
2012-02-01 20:27 ` [PATCH 1/3] udev: improve udev-cache robustness Otavio Salvador
2012-02-01 20:52 ` Otavio Salvador
2012-02-01 20:27 ` [PATCH 2/3] dhcp: move dhcp leases files handling to postinst/postrm Otavio Salvador
2012-02-01 20:57 ` Phil Blundell
2012-02-01 21:01 ` Otavio Salvador
2012-02-02 10:43 ` Phil Blundell
2012-02-02 14:53 ` Richard Purdie
2012-02-02 18:34 ` Otavio Salvador
2012-02-01 20:27 ` [PATCH 3/3] rootfs_ipk.bbclass: fix detection of script runtime requirement Otavio Salvador
2012-02-01 20:59 ` Phil Blundell
2012-02-01 21:03 ` Otavio Salvador
2012-02-02 10:42 ` Phil Blundell
2012-02-02 8:48 ` Martin Jansa [this message]
2012-02-02 14:57 ` [PATCH 0/3] Pending patches in O.S. Systems tree Richard Purdie
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=20120202084816.GE3697@jama.jama.net \
--to=martin.jansa@gmail.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