From: Joshua Lock <josh@linux.intel.com>
To: poky@yoctoproject.org
Subject: Re: gnutls-2.12.14-r3.1 - strange rpm names yocto
Date: Fri, 09 Dec 2011 15:35:20 -0800 [thread overview]
Message-ID: <4EE29B38.3030104@linux.intel.com> (raw)
In-Reply-To: <4EE2887C.3000601@gherzan.ro>
On 09/12/11 14:15, Andrei Gherzan wrote:
> Hello guys,
>
> I've been plying along with yocto lately and managed to understand at a
> decent level it's work-flow and components.
>
> Today wanted to complete an image-core-minimal for arm using packages
> that are not GPLv3 using (found in manual):
> #EXTRA_IMAGE_FEATURES = "debug-tweaks"
> INCOMPATIBLE_LICENSE = "GPLv3"
>
> Further more i wanted to compile gnutls and i think that i came across a
> bug. In the bb file (poky/meta/recipes-support/gnutls/gnutls_2.12.14.bb)
> the rules for pakages are:
> PACKAGES =+ "${PN}-openssl ${PN}-extra ${PN}-bin ${PN}-xx"
>
> FILES_${PN} = "${libdir}/libgnutls.so.*"
> FILES_${PN}-bin = "${bindir}/gnutls-serv \
> ${bindir}/gnutls-cli \
> ${bindir}/srptool \
> ${bindir}/psktool \
> ${bindir}/p11tool \
> ${bindir}/certtool \
> ${bindir}/gnutls-srpcrypt"
>
> FILES_${PN}-dev += "${bindir}/*-config ${bindir}/gnutls-cli-debug"
> FILES_${PN}-extra = "${libdir}/libgnutls-extra.so.*"
> FILES_${PN}-openssl = "${libdir}/libgnutls-openssl.so.*"
> FILES_${PN}-xx = "${libdir}/libgnutlsxx.so.*"
>
> So the rpms should be named gnutls-dev, gnutls-bin etc etc.
> Well... this is not true cause in the
> tmp/work/armv5te-poky-linux-gnueabi/gnutls-2.12.14-r3.1/deploy-rpms
> directory i found:
>
> drwxr-xr-x 2 agherzan agherzan 4096 2011-12-09 23:47 .
> drwxrwxr-x 3 agherzan agherzan 4096 2011-12-09 23:46 ..
> -rw-r--r-- 1 agherzan agherzan 306281 2011-12-09 23:47
> libgnutls26-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 107347 2011-12-09 23:47
> libgnutls-bin-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 1667211 2011-12-09 23:47
> libgnutls-dbg-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 63017 2011-12-09 23:47
> libgnutls-dev-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 799229 2011-12-09 23:47
> libgnutls-doc-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 17962 2011-12-09 23:47
> libgnutls-extra26-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 12240 2011-12-09 23:47
> libgnutls-locale-cs-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 7992 2011-12-09 23:47
> libgnutls-locale-de-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 10241 2011-12-09 23:47
> libgnutls-locale-en+boldquot-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 10192 2011-12-09 23:47
> libgnutls-locale-en+quot-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 12095 2011-12-09 23:47
> libgnutls-locale-fr-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 11857 2011-12-09 23:47
> libgnutls-locale-it-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 10325 2011-12-09 23:47
> libgnutls-locale-ms-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 11858 2011-12-09 23:47
> libgnutls-locale-nl-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 11973 2011-12-09 23:47
> libgnutls-locale-pl-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 11773 2011-12-09 23:47
> libgnutls-locale-sv-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 12338 2011-12-09 23:47
> libgnutls-locale-vi-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 10521 2011-12-09 23:47
> libgnutls-locale-zh-cn-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 18005 2011-12-09 23:47
> libgnutls-openssl27-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 1795460 2011-12-09 23:47
> libgnutls-staticdev-2.12.14-r3.1.armv5te.rpm
> -rw-r--r-- 1 agherzan agherzan 18524 2011-12-09 23:47
> libgnutlsxx27-2.12.14-r3.1.armv5te.rpm
>
> More infos: I'm using multithreading building and my last commit in poky
> is "commit af7fbd6083f4b5f1770e58fe0a2262951037c176."
>
> I just cannot understand how these names are built. More, what are
> libgnutls-openssl27 and libgnutlsxx27?
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
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-12-09 23:35 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 [this message]
2011-12-10 0:02 ` Andrei Gherzan
2011-12-10 4:08 ` Mark Hatle
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=4EE29B38.3030104@linux.intel.com \
--to=josh@linux.intel.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.