All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: gnutls-2.12.14-r3.1 - strange rpm names yocto
Date: Fri, 9 Dec 2011 22:08:50 -0600	[thread overview]
Message-ID: <4EE2DB52.5050107@windriver.com> (raw)
In-Reply-To: <4EE2A184.6020901@gherzan.ro>

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!  ;)

--Mark

> --
> *Andrei Gherzan*, Engineer
> mobile +40.744.478.414 fax +40.031.816.28.12
> Email: andrei@gherzan.ro
> Email: andrei.gherzan@windriver.com
> Romania
>
> Acest e-mail reprezinta corespondenta pentru care dumneavoastra v-ati exprimat
> acordul si se supune politicii noastre de anti-spamming.
> Daca totusi considerati ca acest email reprezinta spamming va rugam sa ne
> contactati folosind e-mail-ul info@gherzan.ro. Multumim.
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky



  reply	other threads:[~2011-12-10  4:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 22:15 gnutls-2.12.14-r3.1 - strange rpm names yocto Andrei Gherzan
2011-12-09 23:35 ` Joshua Lock
2011-12-10  0:02   ` Andrei Gherzan
2011-12-10  4:08     ` Mark Hatle [this message]
2011-12-11  9:48       ` Richard Purdie
2011-12-19 14:05 ` Andrei Gherzan
2011-12-19 17:29   ` Saul Wold
2011-12-20 11:09     ` Andrei Gherzan
2011-12-20 18:18       ` Saul Wold
2011-12-20 23:41         ` Andrei Gherzan
2011-12-21  5:55           ` Saul Wold
2011-12-21  9:47             ` Andrei Gherzan
2011-12-21 18:54               ` Andrei Gherzan
2011-12-21 20:23                 ` Andrei Gherzan
2011-12-11 10:58 Foinel
2011-12-11 16:10 ` Andrei Gherzan
2011-12-11 22:12   ` Richard Purdie
2011-12-12 14:54     ` Foinel
2011-12-12 22:42       ` Andrei Gherzan
2011-12-12 23:21         ` Khem Raj
2011-12-13  9:18           ` Foinel
2011-12-13  9:40             ` Anders Darander
2011-12-13 10:04               ` Foinel
2011-12-13 19:52                 ` Khem Raj
2011-12-14  7:26                   ` Andrei Gherzan
2011-12-13 10:22           ` Foinel
2011-12-13 15:23             ` Richard Purdie
2011-12-14 10:54               ` Foinel

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=4EE2DB52.5050107@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.