Re: [PATCH v3] dbus: include dbus-launch in the main dbus package

[Paul Eggleton <paul.eggleton@linux.intel.com>]

On Thursday 26 July 2012 14:38:59 Koen Kooi wrote:
> Op 26 jul. 2012, om 14:32 heeft Paul Eggleton het volgende geschreven:
> > On Thursday 26 July 2012 14:29:14 Koen Kooi wrote:
> >> Op 26 jul. 2012, om 14:00 heeft Burton, Ross het volgende geschreven:
> >>> On 26 July 2012 12:55, Koen Kooi <koen@dominion.thruhere.net> wrote:
> >>>> It would be nice if other layers that have RDEPENDS_foo = "dbus-x11"
> >>>> keep
> >>>> working till their maintainers get around fixing them. Note that you
> >>>> might need to do a -c cleansstate on dbus first to trigger any errors.>
> >>> 
> >>> Yes, and isn't that what the RPROVIDES is for?
> >> 
> >> I'm not sure if bitbake can map RPROVIDES to PROVIDES, I vaguely remember
> >> that it doesn't, but it will pick it up *after* do_package has run. I
> >> broke
> >> OE way too many times doing things like that :)
> > 
> > Why would it need to if we're talking about RDEPENDS and more specifically
> > RDEPENDS defined before do_package?
> 
> Because AIUI RDEPENDS get resolved to build the runqueue, so you can't do
> RDEPENDS_foo = "I-don't-exist". If that's not the case I'll shut up :)

Without being too concerned with implementation details, I think it's as 
simple as this: if recipe A has foo in RDEPENDS_${PN} and recipe B has foo in 
RPROVIDES_${PN} then the runtime dependency is considered satisfied and things 
will work. You don't have to specify foo in PROVIDES unless something else has 
foo in DEPENDS.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre