From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH][poky-extras] meta-kernel-dev: allow for dangling bbappend files
Date: Tue, 12 Jul 2011 00:49:05 -0400 [thread overview]
Message-ID: <4E1BD241.1070106@windriver.com> (raw)
In-Reply-To: <4E1BB620.6040301@linux.intel.com>
On 11-07-11 10:49 PM, Darren Hart wrote:
> With the bitbake commit:
> 7a2a24de094ce8f2e2068bbee6709dfc2cdc69b9
> missing base recipe files for bbappends became an error. Rather than creating a
> separate kernel development layer for every layer containing a new kernel recipe
> name, conditionally set BB_DANGLINGAPPENDS_WARNONLY.
>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> CC: Bruce Ashfield<bruce.ashfield@windriver.com>
Agreed. This is the right solution.
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> CC: Jeff Mitchell<jmitchell@ll.mit.edu>
> ---
> meta-kernel-dev/conf/layer.conf | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/meta-kernel-dev/conf/layer.conf b/meta-kernel-dev/conf/layer.conf
> index 33f1ca5..01e5b15 100644
> --- a/meta-kernel-dev/conf/layer.conf
> +++ b/meta-kernel-dev/conf/layer.conf
> @@ -1,3 +1,7 @@
> +# Avoid having to split this into multiple layers
> +# Allow missing base recipe files for our bbappends
> +BB_DANGLINGAPPENDS_WARNONLY ?= "true"
> +
> # We have a conf and classes directory, add to BBPATH
> BBPATH := "${BBPATH}:${LAYERDIR}"
>
prev parent reply other threads:[~2011-07-12 4:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 2:49 [PATCH][poky-extras] meta-kernel-dev: allow for dangling bbappend files Darren Hart
2011-07-12 4:49 ` Bruce Ashfield [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=4E1BD241.1070106@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=yocto@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.