From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] package.bbclass: convert file depends into pkg depends
Date: Mon, 14 Jul 2014 15:04:49 -0500 [thread overview]
Message-ID: <53C437E1.1020600@windriver.com> (raw)
In-Reply-To: <53C4048D.7090006@windriver.com>
On 7/14/14, 11:25 AM, Robert Yang wrote:
>
> Hello,
>
> Found that eglibc-utils/usr/bin/tzselect is a bash script, should we
> add:
>
> RDEPENDS_eglibc-utils += "bash" ?
>
> The problem is that this would cause bash installed to meta-toolchain,
> the dependencies chain is:
>
> meta-toolchain -> eglibc-utils -> bash
>
> Maybe we should only warn rather than add the RDEPENDS atm, please ?
Hmm at one point I thought someone has re-written tzselect as posix sh, to avoid
the bash dependency.
I'd actually suggest this be a defect and we try to find someone who can fix it.
(I'd like to eliminate bash dependencies in anything core to a tiny system.)
--Mark
> // Robert
>
> On 07/14/2014 06:29 PM, Burton, Ross wrote:
>> On 14 July 2014 10:41, Robert Yang <liezhi.yang@windriver.com> wrote:
>>> + prog_maps = {"/bin/bash": "bash", "/usr/bin/perl": "perl", "/usr/bin/python": "python"}
>>
>> Use something like d.expand("${bindir}/perl") instead of hard-coding paths.
>>
>> Ross
>>
>>
prev parent reply other threads:[~2014-07-14 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:41 [PATCH 0/2] check and convert file depends on bash, perl and python Robert Yang
2014-07-14 9:41 ` [PATCH 1/2] insane.bbclass: QAPATHTEST: check " Robert Yang
2014-07-14 20:02 ` Mark Hatle
2014-07-15 1:24 ` Robert Yang
2014-07-14 9:41 ` [PATCH 2/2] package.bbclass: convert file depends into pkg depends Robert Yang
2014-07-14 10:29 ` Burton, Ross
2014-07-14 10:34 ` Robert Yang
2014-07-14 16:25 ` Robert Yang
2014-07-14 20:04 ` Mark Hatle [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=53C437E1.1020600@windriver.com \
--to=mark.hatle@windriver.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