From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] rootfs_ipk.bbclass: fix unpacked postinst support if no package management
Date: Fri, 17 Feb 2012 20:29:10 +0000 [thread overview]
Message-ID: <1329510550.2591.122.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAP9ODKqgFVA5K6DQG-hZXww+fiFX+H4hGcqfWjn691ng3jgGVA@mail.gmail.com>
On Fri, 2012-02-17 at 18:14 -0200, Otavio Salvador wrote:
> On Fri, Feb 17, 2012 at 18:11, Phil Blundell <philb@gnu.org> wrote:
> We seem to be going in circles here but, to go back to what I
> said at
> the beginning, why can't you use the existing run-postinsts
> recipe
> rather than adding a new script?
>
>
> My image didn't end with it installed. I did a very small image and I
> expect that independently of what I choose, rootfs behave right.
Ah, I see. Yes, that's a fair point. Maybe rootfs_ipk itself should
inject ${ROOTFS_PKGMANAGE_BOOTSTRAP} into the image if it notices that
there are postinsts which require running and no other package manager
is installed. I think it would be better not to have multiple scripts
doing the same thing if we can avoid it, otherwise you end up having to
fix things like ordering issues in all of them independently.
p.
next prev parent reply other threads:[~2012-02-17 20:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 17:47 [PATCH 0/3] Pending O.S. Systems' tree patches Otavio Salvador
2012-02-17 17:47 ` [PATCH 1/3] update-rc.d.bbclass: do nothing for extended cross packages Otavio Salvador
2012-02-17 17:47 ` [PATCH 2/3] rootfs_ipk.bbclass: fix status file location in rootfs Otavio Salvador
2012-02-17 17:47 ` [PATCH 3/3] rootfs_ipk.bbclass: fix unpacked postinst support if no package management Otavio Salvador
2012-02-17 17:51 ` Phil Blundell
2012-02-17 19:06 ` Otavio Salvador
2012-02-17 19:25 ` Phil Blundell
2012-02-17 19:30 ` Otavio Salvador
2012-02-17 19:59 ` Phil Blundell
2012-02-17 20:03 ` Otavio Salvador
2012-02-17 20:11 ` Phil Blundell
2012-02-17 20:14 ` Otavio Salvador
2012-02-17 20:29 ` Phil Blundell [this message]
2012-02-18 3:56 ` Otavio Salvador
2012-02-24 4:06 ` [PATCH 0/3] Pending O.S. Systems' tree patches Saul Wold
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=1329510550.2591.122.camel@x121e.pbcl.net \
--to=philb@gnu.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