Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: 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 15:51:24 +0100	[thread overview]
Message-ID: <ggjnpc$qhg$1@ger.gmane.org> (raw)

Hi,

Recently the FSO developers discovered that they can put

RPROVIDES = "foo"
RCONFLICTS = "foo"

in their fso-foo recipe to have OE install fso-foo instead of foo in 
their fso-image. Great.

The downside: people can't get 'foo' anymore in their image since 
'fso-foo' will _always_ get choosen over 'foo'. Not so great.

Normally it would be just a matter of putting PREFERRED_PROVIDER_foo = 
"foo" in the distro.conf, but that is not an option in this case, since 
when building 'fso-image' I actually want 'fso-foo' instead of 'foo'

My proposal is:

* remove the RPROVIDES, leave the RCONFLICTS
* put 'fso-foo' in IMAGE_INSTALL in fso-images instead of 'foo'
* educate people using RPROVIDES, RCONFLICTS and RREPLACES in recipes

objections?

regards,

Koen




             reply	other threads:[~2008-11-26 14:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 14:51 Koen Kooi [this message]
2008-11-26 16:55 ` preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image 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
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='ggjnpc$qhg$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