Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: what's the rationale for libpcre_8.35 "PROVIDING" pcre?
Date: Mon, 7 Jul 2014 09:31:02 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407070925320.9468@localhost> (raw)


  i might be overthinking this, but ive noticed a number of "lib*"
recipe files that "PROVIDE" the shorter name. case in point -- in the
current oe-core, the recipe file libpcre_8.35.bb explicitly does this:

PROVIDES += "pcre"

is there a reason for this, other than the obvious allowing to use the
shorter name?

  i did notice that, although the name "libpcre" suggests a shared
library, the recipe file clearly creates a number of packages,
including some that provide command-line utilities:

PACKAGES =+ "libpcrecpp libpcreposix pcregrep pcregrep-doc pcretest pcretest-doc"

  so is there anything to this occasional "lib*" renaming, other than
brevity? thanks.

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-07 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 13:31 Robert P. J. Day [this message]
2014-07-08 10:15 ` what's the rationale for libpcre_8.35 "PROVIDING" pcre? 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=alpine.LFD.2.11.1407070925320.9468@localhost \
    --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