[OE-core] packageA rdepends on packageB but it isn't a build dependency warnings

[André Draszik]

Hi,

I am getting above QA warnings for some packages. Simple example - a recipe
packageA with a shell script that calls out to certain other command line
utilities from packageB.

Given packageA is only a shell script, it ought to be enough to simply add
an RDEPENDS on packageB in that recipe. But when I do that, most of the time
(not always it appears, though!) I get the warning from the subject of this
email.
I have even seen the generated IPK package to not have an entry for the runtime
dependency. Again, sometimes, not always.

Is it really necessary in this case to add a DEPENDS, or is there some flag
that can be set or something? I didn't find anything after a quick search...


Cheers,
Andre'