From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image
Date: Wed, 26 Nov 2008 18:03:57 +0000 [thread overview]
Message-ID: <1227722637.19934.36.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <ggk26f$30a$1@ger.gmane.org>
On Wed, 2008-11-26 at 18:49 +0100, Koen Kooi wrote:
> Conflicts: + Replaces: hits another bug in opkg, it will silently pick
> 'fso-foo' over 'foo' when both are in deploy (e.g. build fso-image for
> om-gta02 and x11-image-with-gpsd for om-gta01). We hit this problem when
> the matchbox-*2 was added from poky.
I'm not quite sure what you're saying here. If fso-foo Conflicts,
Replaces, and Provides foo, opkg would be basically correct to install
the former rather than the latter package. What exactly is the
behaviour you're observing?
p.
next prev parent reply other threads:[~2008-11-26 18:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 14:51 preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image Koen Kooi
2008-11-26 16:55 ` Michael 'Mickey' Lauer
2008-11-26 17:28 ` Koen Kooi
2008-11-26 17:40 ` Phil Blundell
2008-11-26 17:49 ` Koen Kooi
2008-11-26 18:03 ` Phil Blundell [this message]
2008-11-26 18:40 ` Koen Kooi
2008-11-26 19:00 ` Phil Blundell
2008-11-26 20:09 ` Koen Kooi
2008-11-26 21:27 ` Phil Blundell
2008-11-27 7:34 ` Koen Kooi
2008-11-26 18:12 ` Sergey Lapin
2008-11-26 18:24 ` Denys Dmytriyenko
2008-11-26 18:33 ` Koen Kooi
2008-11-26 18:45 ` Denys Dmytriyenko
2008-11-26 18:35 ` Phil Blundell
2008-11-28 9:40 ` Koen Kooi
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=1227722637.19934.36.camel@mill.internal.reciva.com \
--to=pb@reciva.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.