From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] lsb: provide lsb-core-ARCH
Date: Sat, 11 Apr 2015 23:27:24 +0100 [thread overview]
Message-ID: <1428791244.6976.9.camel@linuxfoundation.org> (raw)
In-Reply-To: <1428609535-15027-4-git-send-email-dmitry_eremin@mentor.com>
On Thu, 2015-04-09 at 22:58 +0300, Dmitry Eremin-Solenikov wrote:
> Some lsb packages depend on correct lsb-core-ARCH package being
> installed (or rather provided) on the target file system. Provide this
> package name by main lsb package.
>
> Signed-off-by: Dmitry Eremin-Solenikov <dmitry_eremin@mentor.com>
> ---
> meta/recipes-extended/lsb/lsb_4.1.bb | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/meta/recipes-extended/lsb/lsb_4.1.bb b/meta/recipes-extended/lsb/lsb_4.1.bb
> index 1ae1e26..c3a79c0 100644
> --- a/meta/recipes-extended/lsb/lsb_4.1.bb
> +++ b/meta/recipes-extended/lsb/lsb_4.1.bb
> @@ -4,6 +4,10 @@ HOMEPAGE = "http://prdownloads.sourceforge.net/lsb"
> LICENSE = "GPLv2+"
> PR = "r2"
>
> +LSB_CORE = "lsb-core-${TARGET_ARCH}"
> +LSB_CORE_i586 = "lsb-core-ia32"
A _x86 here is probably a better option?
Cheers,
Richard
> +RPROVIDES_${PN} += "${LSB_CORE}"
> +
> # lsb_release needs getopt
> RDEPENDS_${PN} += "${VIRTUAL-RUNTIME_getopt}"
>
> --
> 2.1.4
>
prev parent reply other threads:[~2015-04-11 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 19:58 [PATCH 1/4] groff: add runtime dependency on sed Dmitry Eremin-Solenikov
2015-04-09 19:58 ` [PATCH 2/4] bitbake.conf: add sed-native to ASSUME_PROVIDED Dmitry Eremin-Solenikov
2015-04-09 19:58 ` [PATCH 3/4] security_flags.inc: add more exceptions Dmitry Eremin-Solenikov
2015-04-10 0:28 ` Khem Raj
2015-04-15 9:10 ` Dmitry Eremin-Solenikov
2015-04-16 21:07 ` Khem Raj
2015-04-09 19:58 ` [PATCH 4/4] lsb: provide lsb-core-ARCH Dmitry Eremin-Solenikov
2015-04-11 22:27 ` Richard Purdie [this message]
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=1428791244.6976.9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=dmitry_eremin@mentor.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox