From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: why "PREFERRED_PROVIDER_udev" and not "PREFERRED_PROVIDER_virtual/udev"?
Date: Mon, 30 Aug 2021 03:52:05 -0400 (EDT) [thread overview]
Message-ID: <a9a5b3df-5a2c-c7c-ba3e-9e4ed712cf67@crashcourse.ca> (raw)
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?
rday
next reply other threads:[~2021-08-30 7:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 7:52 Robert P. J. Day [this message]
2021-08-30 16:09 ` [OE-core] why "PREFERRED_PROVIDER_udev" and not "PREFERRED_PROVIDER_virtual/udev"? 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
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=a9a5b3df-5a2c-c7c-ba3e-9e4ed712cf67@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox