Re: [PATCH 1/1] image.bbclass: leave metadata in place if a PM is installed in the image

[Paul Eggleton <paul.eggleton@linux.intel.com>]

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.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre