From: Koen Kooi <k.kooi@student.utwente.nl>
To: 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:49:02 +0100 [thread overview]
Message-ID: <ggk26f$30a$1@ger.gmane.org> (raw)
In-Reply-To: <1227721214.19934.33.camel@mill.internal.reciva.com>
On 26-11-08 18:40, Phil Blundell wrote:
> On Wed, 2008-11-26 at 17:55 +0100, Michael 'Mickey' Lauer wrote:
>> Sounds good overall, however there is still the problem with things like e.g.
>> gpsd. If you remove fso-gpsd's RPROVIDES=gspd, then anything that rdepends on
>> gpsd will bring us gpsd back into the [fso-]image, hence we have a conflict
>> again.
>
> It sounds like you have a namespacing problem here. If there are
> packages which need to depend on some abstract gpsd API or ABI, they
> should probably be Depending on "virtual/gpsd" or the like and this
> virtual package should be Provided by both gpsd and fso-gpsd.
>
> Semi-virtual packages (i.e. a given name existing both as a concrete
> package and as a Provides: in some other package) basically do not work:
> this is partly an implementation problem in opkg but there is also a
> fundamentally insoluble problem with versioning. About the only time
> that adding a Provides: for the same name as an existing concrete
> package is the right thing to do, is when one package completely
> supercedes each other; in this case you would generally also say that
> the new one Replaces: and Conflicts: with the old one.
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.
The good news is that opkg is maintained now so this problem can be fixed :)
regards,
Koen
next prev parent reply other threads:[~2008-11-26 17:52 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 [this message]
2008-11-26 18:03 ` Phil Blundell
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='ggk26f$30a$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox