From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com>,
Bitbake dev Mailing List <bitbake-devel@lists.openembedded.org>
Cc: Phoong Stanley Cheong Kwan <stanley.cheong.kwan.phoong@intel.com>
Subject: Re: [PATCHv2] bitbake-layers: check layer dependencies before adding
Date: Sun, 04 Jun 2017 15:13:11 +0100 [thread overview]
Message-ID: <1496585591.6630.163.camel@linuxfoundation.org> (raw)
In-Reply-To: <1496018646-92426-2-git-send-email-rebecca.swee.fun.chang@intel.com>
On Mon, 2017-05-29 at 08:44 +0800, Chang Rebecca Swee Fun wrote:
> In the original implementation, "bitbake-layers add-layers <layer>"
> succeeded without error checking. This will further introduce
> failures in recipe parsing only when "bitbake" command is executed.
> Adding a meta layer without its dependency layer(s) should failed
> and exit the process gracefully.
>
> Added extra argument "-f" to force add a layer without checking
> layer dependency.
>
> [YOCTO #10913]
>
> Signed-off-by: Phoong Stanley Cheong Kwan <stanley.cheong.kwan.phoong
> @intel.com>
> Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.c
> om>
> ---
> bin/bitbake-layers | 1 +
> lib/bblayers/action.py | 26 ++++++++++++++++++++++----
> 2 files changed, 23 insertions(+), 4 deletions(-)
This patch seems to result in this:
https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/320/steps/Running%20oe-selftest/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2017-06-04 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 0:44 [PATCHv2] bitbake-layers: check layer dependencies before adding Chang Rebecca Swee Fun
2017-05-29 0:44 ` Chang Rebecca Swee Fun
2017-06-04 14:13 ` Richard Purdie [this message]
2017-06-05 6:40 ` Chang, Rebecca Swee Fun
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=1496585591.6630.163.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=rebecca.swee.fun.chang@intel.com \
--cc=stanley.cheong.kwan.phoong@intel.com \
/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.