From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC v2] package.bbclass: enable the use of package_qa_handle_error
Date: Mon, 2 Jul 2012 17:40:37 -0700 [thread overview]
Message-ID: <1341276037-32076-1-git-send-email-sgw@linux.intel.com> (raw)
This will allow the reporting of these errors as either WARNINGs (default)
or ERRORs if installed_vs_shipped is added to the ERROR_QA of the policy
file (such as a <distro_name>.conf file.
V2: found the code I had intended to send instead of that other junk,
was just not watching what I pushed on that one, sorry. (this is edit in
no in the actual commit message)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/classes/package.bbclass | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 0b98c6b..ff2ec96 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -988,9 +988,14 @@ python populate_packages () {
unshipped.append(path)
if unshipped != []:
- bb.warn("For recipe %s, the following files/directories were installed but not shipped in any package:" % pn)
- for f in unshipped:
- bb.warn(" " + f)
+ msg = pn + ": Files/directories were installed but not shipped"
+ skip = (d.getVar('INSANE_SKIP_' + pn, True) or "").split()
+ if "installed_vs_shipped" in skip:
+ bb.note("Package %s skipping QA tests: installed_vs_shipped" % pn)
+ else:
+ package_qa_handle_error("installed_vs_shipped", msg, d)
+ for f in unshipped:
+ package_qa_handle_error("installed_vs_shipped", " " + f, d)
bb.build.exec_func("package_name_hook", d)
--
1.7.10.4
next reply other threads:[~2012-07-03 0:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 0:40 Saul Wold [this message]
2012-07-03 13:55 ` [RFC v2] package.bbclass: enable the use of package_qa_handle_error Chris Larson
2012-07-03 17:12 ` Saul Wold
2012-07-03 19:04 ` Khem Raj
2012-07-03 19:46 ` Chris Larson
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=1341276037-32076-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.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