[OE-core] what's the rationale for libpcre_8.35 "PROVIDING" pcre?

Richard Purdie richard.purdie at linuxfoundation.org
Tue Jul 8 10:15:38 UTC 2014


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




More information about the Openembedded-core mailing list