From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCHv2] bc: use update-alternatives to make dc play nice with busybox
Date: Tue, 03 Apr 2012 15:56:21 -0700 [thread overview]
Message-ID: <4F7B8015.2010406@linux.intel.com> (raw)
In-Reply-To: <1332978770-6323-1-git-send-email-denis@denix.org>
On 03/28/2012 04:52 PM, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko<denys@ti.com>
>
> busybox' default configuration enables dc app, which bc also provides,
> setup update-alternatives to resolve the conflict.
>
> Signed-off-by: Denys Dmytriyenko<denys@ti.com>
> ---
> meta/recipes-extended/bc/bc_1.06.bb | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-extended/bc/bc_1.06.bb b/meta/recipes-extended/bc/bc_1.06.bb
> index 02915e1..283e2d8 100644
> --- a/meta/recipes-extended/bc/bc_1.06.bb
> +++ b/meta/recipes-extended/bc/bc_1.06.bb
> @@ -11,11 +11,14 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>
> SECTION = "base"
> DEPENDS = "flex"
> -PR = "r0"
> +PR = "r1"
>
> SRC_URI = "${GNU_MIRROR}/bc/bc-${PV}.tar.gz"
>
> SRC_URI[md5sum] = "d44b5dddebd8a7a7309aea6c36fda117"
> SRC_URI[sha256sum] = "4ef6d9f17c3c0d92d8798e35666175ecd3d8efac4009d6457b5c99cea72c0e33"
>
> -inherit autotools
> +inherit autotools update-alternatives
> +
> +ALTERNATIVE_LINKS = "${bindir}/dc"
> +ALTERNATIVE_PRIORITY = "100"
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-04-03 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 23:52 [PATCHv2] bc: use update-alternatives to make dc play nice with busybox Denys Dmytriyenko
2012-04-03 22:56 ` Saul Wold [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=4F7B8015.2010406@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=denys@ti.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