From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Henning Heinold <henning@itconsulting-heinold.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] perf: add slang to the dependencies
Date: Fri, 13 Jun 2014 17:43:42 +0100 [thread overview]
Message-ID: <1402677822.562.0.camel@ted> (raw)
In-Reply-To: <1402348889-26065-2-git-send-email-henning@itconsulting-heinold.de>
On Mon, 2014-06-09 at 23:21 +0200, Henning Heinold wrote:
> * some kernels depends on newt, some on slang and some on boths
> * changing TUI_DEFINES is not necessary, because NO_NEWT is
> compatible with all kernels
>
> The patch was sponsored by sysmocom
>
> Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de>
> ---
> meta/recipes-kernel/perf/perf.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/perf/perf.bb b/meta/recipes-kernel/perf/perf.bb
> index ef21b6c..adbecfd 100644
> --- a/meta/recipes-kernel/perf/perf.bb
> +++ b/meta/recipes-kernel/perf/perf.bb
> @@ -15,7 +15,7 @@ require perf-features.inc
>
> BUILDPERF_libc-uclibc = "no"
>
> -TUI_DEPENDS = "${@perf_feature_enabled('perf-tui', 'libnewt', '',d)}"
> +TUI_DEPENDS = "${@perf_feature_enabled('perf-tui', 'libnewt slang', '',d)}"
> SCRIPTING_DEPENDS = "${@perf_feature_enabled('perf-scripting', 'perl python', '',d)}"
Can we put a comment in the recipe about the problem here so that we
remember why we have the dependencies when looking back in the future
please?
Cheers,
Richard
next prev parent reply other threads:[~2014-06-13 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 21:21 [PATCH 0/3] perf packaging improvements and fixes Henning Heinold
2014-06-09 21:21 ` [PATCH 1/3] perf: add slang to the dependencies Henning Heinold
2014-06-13 16:43 ` Richard Purdie [this message]
2014-06-09 21:21 ` [PATCH 2/3] perf: fix broken shell comparsion in do_install Henning Heinold
2014-06-10 0:35 ` Bruce Ashfield
2014-06-10 11:06 ` Henning Heinold
2014-06-09 21:21 ` [PATCH 3/3] perf: split packging Henning Heinold
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=1402677822.562.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=henning@itconsulting-heinold.de \
--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