Re: more nitpicky pedantry: question about DEFAULT_PREFERENCE

Robert P. J. Day

On Mon, 10 Feb 2020, Richard Purdie wrote:

On Sat, 2020-02-08 at 13:48 -0500, rpjday@... wrote:
On Sat, 8 Feb 2020, rpjday@... wrote:
... snip ...
which seems odd as there don't appear to be any other recipes that
provide pkgconfig, and AIUI, the default provider for any recipe is
the recipe with *exactly* the same name as the target -- in this

also wanted to clarify, while the default provider of a dependency
is the recipe with *exactly* that name, i'm assuming (i think i
remember this from somewhere) that if you have a number of recipes
that all provide, say, "virtual/kernel", and you have an explicit
dependency of "virtual/kernel", you *must* supply a

PREFERRED_PROVIDER_virtual/kernel = ...

line, yes? as in, there's no weird processing to figure out which
recipe you'll be arbitrarily handed among the several that could be
The resolution code is deterministic (i.e. it might sort them) but
there is no specific default provider, no.
ah, so if you don't specify a PREFERRED_PROVIDER, then *some*
provider will ultimately be selected, is that it? you just won't have
any gurarantee which one it will be.


Join { to automatically receive all group messages.