From: Phil Blundell <pb@pbcl.net>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image.bbclass: leave metadata in place if a PM is installed in the image
Date: Thu, 05 Sep 2013 14:24:54 +0100 [thread overview]
Message-ID: <1378387494.6940.90.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <20130905131422.GD17481@lpalcu-linux>
On Thu, 2013-09-05 at 16:14 +0300, Laurentiu Palcu wrote:
> Before the rework, the metadata (for opkg at least) was deleted no
> matter what during rootfs generation. So, there's no way this case (no
> 'package-management' in IMAGE_FEATURES and opkg installed) worked
> recently.
>
> Anyway, do we have a better idea? The solution Phil suggested, is not
> quite ok... We'll end up with useless metadata if no PM is installed and
> delayed postinstalls are present or, the other case, have the PM
> installed with no metadata if the PM is installed but we have no delayed
> postinstalls...
What is it that actually causes run-postinsts to fail when opkg is
installed? I guess that's the bit that I'm not understanding at the
moment. As far as I can tell from a quick inspection of run-postinsts
itself, it ought to be unperturbed by opkg's presence and no harm ought
to result.
p.
next prev parent reply other threads:[~2013-09-05 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 7:31 [PATCH 0/1] image.bbclass: leave metadata in place if a PM is installed in the image Laurentiu Palcu
2013-09-05 7:31 ` [PATCH 1/1] " Laurentiu Palcu
2013-09-05 8:15 ` Martin Jansa
2013-09-05 8:57 ` Laurentiu Palcu
2013-09-05 10:43 ` Phil Blundell
2013-09-05 11:11 ` Laurentiu Palcu
2013-09-05 11:37 ` Phil Blundell
2013-09-05 11:40 ` Phil Blundell
2013-09-05 11:59 ` Laurentiu Palcu
2013-09-05 12:07 ` Phil Blundell
2013-09-05 12:19 ` Paul Eggleton
2013-09-05 12:29 ` Phil Blundell
2013-09-05 12:53 ` Paul Eggleton
2013-09-05 13:14 ` Laurentiu Palcu
2013-09-05 13:24 ` Phil Blundell [this message]
2013-09-05 13:25 ` Laurentiu Palcu
2013-09-05 12:42 ` ChenQi
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=1378387494.6940.90.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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