From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC] package.bbclass: enable the use of ERROR_QA
Date: Mon, 2 Jul 2012 15:27:56 -0700 [thread overview]
Message-ID: <1341268076-1331-1-git-send-email-sgw@linux.intel.com> (raw)
This patch allows the use of ERROR_QA to give policy control to distros
for the Installed and not shipped error in packages. installed_vs_shipped
can be set in the distro config file for ERROR_QA.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/classes/package.bbclass | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 10c2f0a..231b01b 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -988,10 +988,19 @@ 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"
+ if "installed_vs_shipped" in = (d.getVar('INSANE_SKIP_' + pn, True) or "").split()
+ bb.note("Package %s skipping Packging installed vs shipped QA test" % pn)
+ continue
+ if "installed_vs_shipped" in (d.getVar("ERROR_QA", True) or "").split():
+ package_qa_handle_error("installed_vs_shipped", msg, d)
+ for f in unshipped:
+ package_qa_handle_error("installed_vs_shipped", " " + f, d)
+ else:
+ bb.warn("For recipe %s, the following files/directories were installed but
+ for f in unshipped:
+ bb.warn(" " + f)
+
bb.build.exec_func("package_name_hook", d)
for pkg in package_list:
--
1.7.10.4
next reply other threads:[~2012-07-02 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 22:27 Saul Wold [this message]
2012-07-02 22:34 ` [RFC] package.bbclass: enable the use of ERROR_QA Phil Blundell
2012-07-02 22:57 ` Saul Wold
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=1341268076-1331-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