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:11:41 +0000 [thread overview]
Message-ID: <1329509501.2591.118.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAP9ODKq7u3Vg+YU8GDMQH3vBw_GPH-Wuq9C7fa=DnEuUo0mr1A@mail.gmail.com>
On Fri, 2012-02-17 at 18:03 -0200, Otavio Salvador wrote:
> On Fri, Feb 17, 2012 at 17:59, Phil Blundell <philb@gnu.org> wrote:
> Well, right, but that's not the run-postinsts package. You
> mentioned
> that opkg-cl wasn't installed so its own postinst is probably
> irrelevant
> here.
>
>
> That's why I added this.
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?
p.
next prev parent reply other threads:[~2012-02-17 20:20 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 [this message]
2012-02-17 20:14 ` Otavio Salvador
2012-02-17 20:29 ` Phil Blundell
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=1329509501.2591.118.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