From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][oe-core 1/3] sysstat: don't run populate-volatile.sh update in do_rootfs or without populate-volatile.sh
Date: Wed, 07 Dec 2011 12:48:54 +0000 [thread overview]
Message-ID: <1323262134.30601.7.camel@ted> (raw)
In-Reply-To: <822c669a79e5f30bda467bc3a6f7b3c92377af22.1323160412.git.Martin.Jansa@gmail.com>
On Tue, 2011-12-06 at 09:35 +0100, Martin Jansa wrote:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/recipes-extended/sysstat/sysstat.inc | 7 ++++++-
> meta/recipes-extended/sysstat/sysstat_10.0.3.bb | 2 +-
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-extended/sysstat/sysstat.inc b/meta/recipes-extended/sysstat/sysstat.inc
> index 2936f96..ca40ab5 100644
> --- a/meta/recipes-extended/sysstat/sysstat.inc
> +++ b/meta/recipes-extended/sysstat/sysstat.inc
> @@ -22,7 +22,12 @@ do_install() {
> }
>
> pkg_postinst_${PN} () {
> - /etc/init.d/populate-volatile.sh update
> + if [ -n "$D" ]; then
> + exit 1
> + fi
> + if [ -e /etc/init.d/populate-volatile.sh ]; then
> + /etc/init.d/populate-volatile.sh update
> + fi
> }
The subject commit message and the code match now, thanks :)
My only other question is whether we need to run this at first boot
time? At first boot after rootfs, populate-volatile will run anyway. We
therefore don't need to run the update as a postinst on device as part
of first boot as well as it will always be covered if present.
I therefore think this should be an "exit 0" and the commit message
should be:
"sysstat: don't run populate-volatile.sh update in do_rootfs, first boot
or without populate-volatile.sh"
Does that make sense?
Cheers,
Richard
next prev parent reply other threads:[~2011-12-07 12:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:34 [PATCH][oe-core 0/3] Small fixes for sysstat, matchbox-session and subversion upgrade Martin Jansa
2011-12-06 8:35 ` [PATCH][oe-core 1/3] sysstat: don't run populate-volatile.sh update in do_rootfs or without populate-volatile.sh Martin Jansa
2011-12-07 12:48 ` Richard Purdie [this message]
2011-12-07 12:50 ` Koen Kooi
2011-12-08 13:03 ` Richard Purdie
2011-12-07 14:57 ` Martin Jansa
2011-12-07 14:59 ` [PATCHv2] sysstat: don't run populate-volatile.sh update in do_rootfs, first boot " Martin Jansa
2011-12-08 15:28 ` Richard Purdie
2011-12-06 8:35 ` [PATCH][oe-core 2/3] subversion: update 1.7.0 to 1.7.1 and force libtool recreation Martin Jansa
2011-12-06 9:16 ` Martin Jansa
2011-12-06 13:43 ` [PATCH] subversion: update 1.7.0 to 1.7.2 " Martin Jansa
2011-12-07 12:42 ` Richard Purdie
2011-12-06 8:35 ` [PATCH][oe-core 3/3] matchbox-session-sato: respect VIRTUAL-RUNTIME_initscripts settings Martin Jansa
2011-12-07 12:42 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2011-11-30 22:56 [PATCH][oe-core 0/3] Small fixes sysstat, squashfs-tools, gconf Martin Jansa
2011-11-30 22:56 ` [PATCH][oe-core 1/3] sysstat: don't run populate-volatile.sh update in do_rootfs or without populate-volatile.sh Martin Jansa
2011-11-30 23:33 ` Richard Purdie
2011-11-30 23:51 ` Martin Jansa
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=1323262134.30601.7.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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