Openembedded Core Discussions
 help / color / mirror / Atom feed
* what's the rationale for libpcre_8.35 "PROVIDING" pcre?
@ 2014-07-07 13:31 Robert P. J. Day
  2014-07-08 10:15 ` Richard Purdie
  0 siblings, 1 reply; 2+ messages in thread
From: Robert P. J. Day @ 2014-07-07 13:31 UTC (permalink / raw)
  To: OE Core mailing list


  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
========================================================================


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: what's the rationale for libpcre_8.35 "PROVIDING" pcre?
  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
  0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2014-07-08 10:15 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: OE Core mailing list

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



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-07-08 10:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox