From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rootfs_ipk: respect ONLINE_PACKAGE_MANAGEMENT
Date: Tue, 24 May 2011 15:16:16 +0100 [thread overview]
Message-ID: <1306246576.2525.194.camel@phil-desktop> (raw)
In-Reply-To: <1306246336.3424.929.camel@rex>
On Tue, 2011-05-24 at 15:12 +0100, Richard Purdie wrote:
> I think allowing selection of this at image generation time is the more
> powerful way to handle this. It could be we go through a step of
> forcibly removing packages we don't want from the rootfs such as
> update-rc.d, or we can tell the package manager to ignore the dependency
> which is probably neater.
>
> I have to admit the update-rc.d change was concerning and this does feel
> like a better way to handle it.
Yeah. The downside to this is that it will require extra
package-manager-specific hackery in each of the rootfs backends, since
there isn't any portable way to either forcibly remove a package or to
get a dependency disregarded. But I guess I can make it work for ipkg
easily enough and we can worry about the others later.
p.
next prev parent reply other threads:[~2011-05-24 14:19 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
2011-05-24 13:59 ` Phil Blundell
2011-05-24 14:12 ` Richard Purdie
2011-05-24 14:16 ` Phil Blundell [this message]
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=1306246576.2525.194.camel@phil-desktop \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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