Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: curious about setting of PROVIDES in bitbake.conf
Date: Wed, 18 Jun 2014 18:35:09 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1406181834470.11766@localhost> (raw)
In-Reply-To: <3485367.eXfHHFnm7Z@peggleto-mobl5.ger.corp.intel.com>

On Wed, 18 Jun 2014, Paul Eggleton wrote:

> On Wednesday 18 June 2014 09:10:00 Robert P. J. Day wrote:
> >   from current bitbake.conf file:
> >
> > PROVIDES = ""
> > PROVIDES_prepend = "${PN} "
> >
> > is there a reason that PROVIDES is set to null, only to immediately
> > set it based on the following line? is there some subtle issue this is
> > meant to address?
>
> I think the intention is to set the initial value to blank, and
> ensure that ${PN} is the first item in the list (since _prepend gets
> applied later). If you just simply had PROVIDES = "${PN}" then it
> could be overridden somewhere else such that ${PN} was not in
> PROVIDES at all, which would be counter-intuitive.

  ah, of course, i should have thought of that. duh.

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-06-18 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 13:10 curious about setting of PROVIDES in bitbake.conf Robert P. J. Day
2014-06-18 15:50 ` Paul Eggleton
2014-06-18 22:35   ` Robert P. J. Day [this message]

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.1406181834470.11766@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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