Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "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:14:23 +0300	[thread overview]
Message-ID: <20130905131422.GD17481@lpalcu-linux> (raw)
In-Reply-To: <3397753.WTGSduA6kl@helios>

On Thu, Sep 05, 2013 at 01:53:44PM +0100, Paul Eggleton wrote:
> On Thursday 05 September 2013 13:29:34 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.
> > 
> > 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?
> 
> The reason I reopened the bug (the final comment) is that I had a situation 
> recently where I had got opkg installed in an image via dependencies and I did 
> not have package-management in IMAGE_FEATURES. The result was that 
> postinstalls to be run on first boot just silently did not work, which is not 
> good behaviour.
> 
> Now, with the image I was dealing with I needed to add package-management to 
> IMAGE_FEATURES anyway; but things shouldn't just silently break because the 
> package manager happens to be installed especially as it may not be 
> immediately clear to the user that the latter had even happened. I'm pretty 
> sure this didn't used to be an issue.
Well, it's present since denzil anyway. You confirmed it yourself Paul:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4484#c13

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...

Thanks,
Laurentiu

> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre


  reply	other threads:[~2013-09-05 13:14 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 [this message]
2013-09-05 13:24                         ` Phil Blundell
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=20130905131422.GD17481@lpalcu-linux \
    --to=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