All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: looking for good example of PREFERRED_PROVIDER_* ... udev/systemd?
Date: Tue, 8 Jul 2014 09:06:06 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407080852470.3046@localhost> (raw)


  currently working through chapter 2 of the bitbake user manual, and
my first thought is that sections 2.3 and 2.4 -- Providers, followed
by Preferences, would make more sense in the reverse order. IMHO,
selecting a preferred version for a recipe is fairly straightforward
and a reader should be able to understand that easily, and there are
lots of good examples of that. the notion of recipes "providing" an
alternate name, however, strikes me as at least a bit more involved
and should take a little more explanation. anyway, that's just my
thinking.

  along those lines, i was looking through the oe-core layer for a
simple example of PREFERRED_PROVIDER and it seems that "systemd"
providing "udev" was a good example, so i took my sample build of
core-image-minimal for qemux86, and just added to my local.conf the
line:

  PREFERRED_PROVIDER_udev = "systemd"

but now, i'm curious ... is there a "bitbake" subcommand that will
show me the effect of that setting? i'm looking at the current bitbake
command-line options and don't immediately see a way to ask for a list
of preferred provider overrides. is there any bitbake command that
will now display that "udev" is being provided by "systemd"?

  my apologies if this is a silly question and i'm overlooking the
obvious.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


                 reply	other threads:[~2014-07-08 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.2.11.1407080852470.3046@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=bitbake-devel@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 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.