From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] why "PREFERRED_PROVIDER_udev" and not "PREFERRED_PROVIDER_virtual/udev"?
Date: Tue, 31 Aug 2021 10:23:31 +0100 [thread overview]
Message-ID: <6bb80d28a94f447ec4ecfaef4f04e818b0041835.camel@linuxfoundation.org> (raw)
In-Reply-To: <a9a5b3df-5a2c-c7c-ba3e-9e4ed712cf67@crashcourse.ca>
On Mon, 2021-08-30 at 03:52 -0400, Robert P. J. Day wrote:
> i was going to extend section 3.3.17, "Using Virtual Providers",
> with an intro example using "udev" until i realized that that example
> doesn't use the "virtual/" notation. so ... why not? is there some
> distinction between other components that use the "virtual/" prefix,
> but a reason that one does not specify:
>
> PROVIDES = "virtual/udev"
>
> rather than just:
>
> PROVIDES = "udev"
>
> and then use the corresponding PREFERRED_PROVIDER_virtual/udev
> notation?
The "virtual/" namespace is just a way of namespacing some key dependencies
outside of the direct recipe namespace.
virtual/libc is a better example and there are a few toolchain related ones.
There are several different libc implementations and virtual/libc just says you
want one without being specific.
Cheers,
Richard
next prev parent reply other threads:[~2021-08-31 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:52 why "PREFERRED_PROVIDER_udev" and not "PREFERRED_PROVIDER_virtual/udev"? Robert P. J. Day
2021-08-30 16:09 ` [OE-core] " Khem Raj
2021-08-31 8:27 ` Robert P. J. Day
2021-08-31 9:24 ` Richard Purdie
2021-08-31 9:23 ` Richard Purdie [this message]
[not found] <16A0063E8A02B067.22970@lists.openembedded.org>
2021-08-30 8:11 ` Robert P. J. Day
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=6bb80d28a94f447ec4ecfaef4f04e818b0041835.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.