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

[Phil Blundell]

On Thu, 2013-09-05 at 12:37 +0100, Phil Blundell wrote:
> On Thu, 2013-09-05 at 14:11 +0300, Laurentiu Palcu wrote:
> > This solution is the most decent I could find in order to address this:
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4484
> > in this stage of 1.5 release. Other ideas are always welcome.
> 
> I couldn't quite follow the long and complicated history of that bug,
> but based on the description and the contents of comment #1 it sounds as
> though the bug is at best tangentially related to this issue.
> 
> In the case where you have postinsts on the target but package
> management is disabled, rootfs_ipk should be installing run-postinsts
> (not opkg) and in that case it doesn't seem like this patch will help.
> 
> It looks as though this breakage was probably introduced by
> 928df79cd3964f775c4c6e4283ef84b8882f9328 which moved the call to
> remove_packaging_data_files() from rootfs_ipk (which was only calling it
> if it knew that all postinsts had already been completed) to
> image.bbclass (which doesn't have that knowledge and will call it
> irrespective of what state the postinsts are in).

Actually, that last sentence is slightly incorrect.  image.bbclass does
have the knowledge, it just seems to be failing to act on it.  So
perhaps the easiest fix for the time being is simply to move the
remove_packaging_data_files call in rootfs_uninstall_unneeded () a few
lines higher up so that it's inside the "if [ -z $(delayed_postinsts) ]"
block.

p.