Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.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 17:40:14 +0000	[thread overview]
Message-ID: <1227721214.19934.33.camel@mill.internal.reciva.com> (raw)
In-Reply-To: <200811261755.53197.mickey@vanille-media.de>

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.

p.





  parent reply	other threads:[~2008-11-26 17:43 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 [this message]
2008-11-26 17:49     ` Koen Kooi
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=1227721214.19934.33.camel@mill.internal.reciva.com \
    --to=pb@reciva.com \
    --cc=openembedded-devel@lists.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