public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
	Khem Raj <raj.khem@gmail.com>
Cc: 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:24:35 +0100	[thread overview]
Message-ID: <12cae25e667c774400af83ff3a860f7eb88510ac.camel@linuxfoundation.org> (raw)
In-Reply-To: <76f5fe9-f9a2-bed4-6cd5-8d5749c95dce@crashcourse.ca>

On Tue, 2021-08-31 at 04:27 -0400, Robert P. J. Day wrote:
> On Mon, 30 Aug 2021, Khem Raj wrote:
> 
> > On Mon, Aug 30, 2021 at 12:52 AM Robert P. J. Day <rpjday@crashcourse.ca> 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?
> > 
> > we also have VIRTUAL-RUNTIME_dev_manager which spans across systemd to mdev
> > so I guess we could but perhaps we already have this functionality
> 
>   a followup, perhaps silly question -- is there anything special
> about the "virtual/" prefix in the sense of being a provider? i mean,
> other than being more aesthetically obvious?

Not really, it just signifies particular groups like the libc example I mention
in another mail.

Cheers,

Richard


  reply	other threads:[~2021-08-31  9:24 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 [this message]
2021-08-31  9:23 ` Richard Purdie
     [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=12cae25e667c774400af83ff3a860f7eb88510ac.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox