From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] rootfs_ipk: Avoid leaving run-postinsts around if online package management is disabled
Date: Mon, 24 Sep 2012 11:27:15 +0100 [thread overview]
Message-ID: <1348482435.4654.17.camel@ted> (raw)
In-Reply-To: <1348256558.4444.194.camel@x121e.pbcl.net>
On Fri, 2012-09-21 at 20:42 +0100, Phil Blundell wrote:
> If all postinsts have already been run during rootfs construction then
> there's no point in having run-postinsts in the installed system.
> Clean it up at the same time that update-rc.d and suchlike are being
> removed.
>
> Signed-off-by: Phil Blundell <pb@pbcl.net>
> ---
> v2: per suggestion from Paul Eggleton, don't refer to O_P_M in subject
> line since oe-core doesn't use it anymore
>
> meta/classes/rootfs_ipk.bbclass | 14 ++++++++++++--
> 1 files changed, 12 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-24 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 19:42 [PATCH v2] rootfs_ipk: Avoid leaving run-postinsts around if online package management is disabled Phil Blundell
2012-09-24 10:27 ` Richard Purdie [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=1348482435.4654.17.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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