Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Phil Blundell <philb@brightsign.biz>,
	Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: 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 13:19:05 +0100	[thread overview]
Message-ID: <3518999.x3yV6XY4Eo@helios> (raw)
In-Reply-To: <1378382840.6940.78.camel@phil-desktop.brightsign>

On Thursday 05 September 2013 13:07:20 Phil Blundell wrote:
> On Thu, 2013-09-05 at 06:59 -0500, Laurentiu Palcu wrote:
> > On Thu, Sep 05, 2013 at 12:40:26PM +0100, Phil Blundell wrote:
> > > 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.
> > 
> > What you're suggesting means that we will have the PM metadata present
> > if there are delayed postinstalls present. But, since the PM is not
> > present, what's the use of that?
> 
> Well, er, that it will make the postinstalls work.  Isn't that exactly
> the problem here?

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?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-09-05 12:19 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 [this message]
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
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=3518999.x3yV6XY4Eo@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=laurentiu.palcu@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@brightsign.biz \
    /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