From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: what's the rationale for libpcre_8.35 "PROVIDING" pcre?
Date: Tue, 08 Jul 2014 11:15:38 +0100 [thread overview]
Message-ID: <1404814538.1458.60.camel@ted> (raw)
In-Reply-To: <alpine.LFD.2.11.1407070925320.9468@localhost>
On Mon, 2014-07-07 at 09:31 -0400, Robert P. J. Day wrote:
> 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.
I suspect the recipe was once called "pcre" but was renamed and the
PROVIDES was for compatibility. There might be something in the history
about that.
Cheers,
Richard
prev parent reply other threads:[~2014-07-08 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 13:31 what's the rationale for libpcre_8.35 "PROVIDING" pcre? Robert P. J. Day
2014-07-08 10:15 ` Richard Purdie [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=1404814538.1458.60.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--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