All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: is it "PROVIDES =" or "PROVIDES +=" for setting an alternate name?
Date: Sat, 12 Jul 2014 07:28:44 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407120725360.20531@localhost> (raw)


  i notice that the OE-core codebase likes to mix these two forms of
using PROVIDES. for instance, for a number of libraries to provide
their basename, i see stuff like:

recipes-graphics/xorg-lib/libxmu_1.1.2.bb:PROVIDES = "xmu"
recipes-graphics/xorg-lib/libice_1.0.8.bb:PROVIDES = "ice"
recipes-graphics/xorg-lib/libxdamage_1.1.4.bb:PROVIDES = "xdamage"
recipes-graphics/xorg-lib/libxfont_1.4.7.bb:PROVIDES = "xfont"
recipes-graphics/xorg-lib/libxdmcp_1.1.1.bb:PROVIDES = "xdmcp"

  on the other hand, there is the occasional example of the same thing
that uses "PROVIDES +=" instead:

recipes-support/libpcre/libpcre_8.35.bb:PROVIDES += "pcre"

is there a deliberate distinction made in the recipes between these
two forms?

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-12 11:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-12 11:28 Robert P. J. Day [this message]
2014-07-12 20:07 ` is it "PROVIDES =" or "PROVIDES +=" for setting an alternate name? Christopher Larson
2014-07-12 20:38   ` 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=alpine.LFD.2.11.1407120725360.20531@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-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.