[poky] gnutls-2.12.14-r3.1 - strange rpm names yocto

[Richard Purdie]

On Fri, 2011-12-09 at 22:08 -0600, Mark Hatle wrote:
> On 12/9/11 6:02 PM, Andrei Gherzan wrote:
> >
> >> This looks like our debian-style package renaming, which renames
> >> libraries to include the lib prefix.
> >>
> >> We have a brief blurb about it here:
> >> http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-classes-debian
> >>
> >> Regards,
> >> Joshua
> >
> > Yes it looks like. But here is the problem: i included this pkg in IMAGE-INSTALL
> > and i found library from -extra with even if
> > LICENSE_${PN}-extra = "GPLv3+"
> >
> > And i think that this could be because of this name style change.
> 
> There are two issues here.  The first is that IMAGE_INSTALL is the binary 
> package name.  This name can be munged with the renaming as Joshua mentioned. 
> Most people assume that this name matches the source recipe name.  So there is 
> confusion to deal with.
> 
> The other issue is that any place a user is asked to list a -binary- package 
> name, it should go through the same munging process as it does when things are 
> generated.  The IMAGE_INSTALL does not do this at this time.  (It -really- 
> should!)  This has been on my list of things to work on for a while now, but I 
> have not had the time to get to it.
> 
> Patches are welcome!  ;)

To quote image.bbclass:

export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${FEATURE_INSTALL}"

python () {
    # If we don't do this we try and run the mapping hooks while parsing which is slow
    # bitbake should really provide something to let us know this...
    if d.getVar('BB_WORKERCONTEXT', True) is not None:
        runtime_mapping_rename("PACKAGE_INSTALL", d)
        runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)
}

so as far as I know, the remapping does work.

Cheers,

Richard