diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-01-20 22:44:33 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-01-20 22:44:33 +0000 |
commit | d4f537965b3a530ca7ed3bce206abbff810031e8 (patch) | |
tree | e97a327c1f484ac0d8f7eaef4b1d51489d38a65d /meta/recipes-kernel/lttng | |
parent | 1d1f2d36c4a1c503b5fb32c8134edcc8ea5f1915 (diff) | |
download | openembedded-core-d4f537965b3a530ca7ed3bce206abbff810031e8.tar.gz openembedded-core-d4f537965b3a530ca7ed3bce206abbff810031e8.tar.bz2 openembedded-core-d4f537965b3a530ca7ed3bce206abbff810031e8.tar.xz openembedded-core-d4f537965b3a530ca7ed3bce206abbff810031e8.zip |
bitbake/providers.py: Fix runtime providers problems
Take a real world testcase where you have two recipes, each of which
contains PACKAGES_DYNAMIC = "gdk-pixbuf-loaders-*" and recipes which
RDEPEND on some gdk-pixbuf-loaders-xxx package. To select between these
you need to set a PREFERRED_PROVIDER.
These are specified in the PN namespace so the locgical conclusion is
that setting PREFERRED_PROVIDER_gdk-pixbuf = "gtk+" should work. It
doesn't and instead checks crazy things.
The code was correctly finding the two possible providers, gtk+ and
gdk-pixbuf. It was however only accepting PREFERRED_PROVIDER_gtk+
= "gdk-pixbuf" to resolve this problem which reads as the exact
opposite to what was wanted.
This patch changes the code to do something that makes sense. I suspect
that before these changes it was pretty much a null operation rubber
stamping the single provider case. For Poky at least it exposes a few
cases where -nativesdk recipes were providing the same things as their
normal counterparts but these are genuine bugs in the metadata.
I've also attempted to make the multiple provider error message human
readable as I counldn't understand it and I doubt anyone else could
either.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/lttng')
0 files changed, 0 insertions, 0 deletions