From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Cui, Dexuan" <dexuan.cui@intel.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
'Martin Jansa' <martin.jansa@gmail.com>
Subject: Re: [PATCH 1/1] die if a .bbappend file matches no existing .bb recipe
Date: Wed, 29 Jun 2011 17:14:57 +0100 [thread overview]
Message-ID: <1309364097.20015.414.camel@rex> (raw)
In-Reply-To: <1865303E0DED764181A9D882DEF65FB6A167F0C723@shsmsx502.ccr.corp.intel.com>
On Thu, 2011-06-30 at 00:03 +0800, Cui, Dexuan wrote:
> Sorry -- what's the conclusion?
> Keeping the v2 patch
> (http://git.pokylinux.org/cgit/cgit.cgi/poky-contrib/commit/?h=dcui/bb-v2&id=2a520959f71ec2cd80ed2088bfcf082631161a1a)
> , or changing bb.error() to bb.warn()?
Where you have:
bb.error('No recipes available for:\n%s' % '\n'.join(appendlines))
this would become something like:
msg = 'No recipes available for:\n%s' % '\n'.join(appendlines)
if d.getVar("BB_DANGLINGAPPENDS_WARNONLY", False):
bb.warn(msg)
else:
bb.fatal(msg)
which means we can have a strong default but advanced
users/distros/whoever can avoid this.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-29 16:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 4:34 [PATCH 0/1] die if a .bbappend file matches no existing .bb recipe Dexuan Cui
2011-06-20 4:34 ` [PATCH 1/1] " Dexuan Cui
[not found] ` <BANLkTinCB95DBHinewz+A1a7BHiZJzV1Mg@mail.gmail.com>
2011-06-20 7:29 ` Cui, Dexuan
2011-06-24 18:16 ` Chris Larson
2011-06-24 18:38 ` Denys Dmytriyenko
2011-06-27 13:49 ` Richard Purdie
2011-06-27 14:05 ` Chris Larson
2011-06-28 7:35 ` Cui, Dexuan
2011-06-28 12:34 ` Richard Purdie
2011-06-27 13:06 ` Paul Eggleton
2011-06-28 12:39 ` Richard Purdie
2011-06-29 16:03 ` Cui, Dexuan
2011-06-29 16:14 ` Richard Purdie [this message]
2011-06-29 16:28 ` Cui, Dexuan
2011-06-29 16:51 ` Denys Dmytriyenko
2011-07-18 14:27 ` Martin Jansa
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=1309364097.20015.414.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=dexuan.cui@intel.com \
--cc=martin.jansa@gmail.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.