Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <pb@pbcl.net>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rootfs_ipk: respect ONLINE_PACKAGE_MANAGEMENT
Date: Thu, 19 May 2011 16:08:24 +0100	[thread overview]
Message-ID: <1305817704.3424.531.camel@rex> (raw)
In-Reply-To: <1305817446.18415.193.camel@lenovo.internal.reciva.com>

On Thu, 2011-05-19 at 16:04 +0100, Phil Blundell wrote:
> On Thu, 2011-05-19 at 13:16 +0100, Richard Purdie wrote:
> > So if we:
> > 
> > a) Only add ROOTFS_PKGMANAGE_BOOTSTRAP if postinstalls were present
> > b) Add the read-only-rootfs option we discussed which errors if 
> >    postinstalls are present
> > 
> > we end up a lot closer to where you want to be.
> 
> Yes, sounds reasonable.  And I think we could then eliminate
> remove_packaging_data_files() altogether, in favour of having the right
> thing happen automatically during rootfs construction, which would
> probably be a good thing too.

Agreed, I think we have a plan :)

Cheers,

Richard




  reply	other threads:[~2011-05-19 15:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 13:55 [PATCH] rootfs_ipk: respect ONLINE_PACKAGE_MANAGEMENT Phil Blundell
2011-05-17 14:24 ` Richard Purdie
2011-05-17 14:50   ` Phil Blundell
2011-05-17 16:22     ` Richard Purdie
2011-05-18 15:37       ` Phil Blundell
2011-05-19 10:15         ` Richard Purdie
2011-05-19 10:31           ` Phil Blundell
2011-05-19 11:21             ` Richard Purdie
2011-05-19 11:41               ` Phil Blundell
2011-05-19 12:16                 ` Richard Purdie
2011-05-19 15:04                   ` Phil Blundell
2011-05-19 15:08                     ` Richard Purdie [this message]
2011-05-24 13:59                       ` Phil Blundell
2011-05-24 14:12                         ` Richard Purdie
2011-05-24 14:16                           ` Phil Blundell
2011-05-19 16:58               ` Chris Larson

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=1305817704.3424.531.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --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