From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Phil Blundell <pb@pbcl.net>
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, 5 Sep 2013 16:25:04 +0300 [thread overview]
Message-ID: <20130905132503.GE17481@lpalcu-linux> (raw)
In-Reply-To: <1378384174.6940.86.camel@phil-desktop.brightsign>
On Thu, Sep 05, 2013 at 01:29:34PM +0100, Phil Blundell wrote:
> On Thu, 2013-09-05 at 07:19 -0500, Paul Eggleton wrote:
> > I'm clearly missing something here. If we have a generic mechanism to run
> > postinstall scripts now, and "package-management" is not in IMAGE_FEATURES,
> > why do we need or want the package manager to be in control of running the
> > postinstalls?
>
> We don't. The postinsts should be getting run by run-postinsts.
Ok, I guess I forgot to mention why the issue mentioned by Paul happens
and run-postinsts doesn't do its job.
Well, as it happens, opkg postinstall creates a S98run-postinsts script
in rcS.d that will overwrite run-postinsts one.
We could fix that by making opkg create the script on position 97 and
both scripts will run in this case. Opkg one will fail, since there is
no metadata available, but run-postinsts will work because the
postinstalls are saved in /etc/(ipk|deb|rpm)_postinsts directory.
The only 'issue' remaining is the lack of metadata if one chooses to
manually install a PM when 'package-management' is disabled.
Now that I think about it, this might be a better alternative. But I
didn't test it though. It just came to my mind...
What do you think?
Laurentiu
>
> I must admit I still don't entirely understand what the problem is that
> Laurentiu is trying to fix with his patch, and the description in the
> Yocto bugzilla remains opaque to me. Can you clarify what exactly it is
> that's currently going wrong?
>
> p.
>
>
next prev parent reply other threads:[~2013-09-05 13:25 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
2013-09-05 13:25 ` Laurentiu Palcu [this message]
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=20130905132503.GE17481@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=pb@pbcl.net \
/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