From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Paul Eggleton
<public-paul.eggleton-VuQAYsv1563Yd54FQh9/CA@lo.gmane.org>,
Dmitry Eremin-Solenikov
<public-dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org>
Subject: Re: [PATCH 17/17] package.bbclass: make unshipped files a fatal error
Date: Thu, 22 Sep 2011 13:50:31 +0400 [thread overview]
Message-ID: <4E7B04E7.1000204@gmail.com> (raw)
In-Reply-To: <201109221045.22340.paul.eggleton@linux.intel.com>
Hello,
On 09/22/2011 01:45 PM, Paul Eggleton wrote:
> On Thursday 22 September 2011 07:36:23 Dmitry Eremin-Solenikov wrote:
>> Nice idea! On the rights of a feature request:
>> It would be nice to allow user to:
>> 1) specify the severity of the QA problems (warn, error, fatal) on a
>> global + per-qa-check level
>
> To affect the severity of warnings on a global basis you should be able to use
> ERROR_QA / WARN_QA, although I have not tried this.
>
>> 2) specify an override for some of the checks, so that the packager
>> can specify that
>> e.g. QA check for .so links in a non-dev packages should be ignored
>> for cgroups-pam package for /lib/security/pam*.so lib.
>
> For per-package, you can set for example INSANE_SKIP_${PN} += "dev-so" to
> disable the .so links in non-dev package QA warning.
>
> More details (e.g. the name for each QA check) can be found in insane.bbclass.
This is a too big handle. Ideally I'd like to be able to whitelist on
the file level, rather than on the package/test level.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-09-22 9:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 18:39 [PATCH 01/17] icecc-create-env: rename to -native Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 02/17] icecc.bbclass: fix handling of nativesdk and cross-canadian packages Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 03/17] insane.bbclass: don't warn on .so files in -nativesdk packages Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 04/17] avahi: include dbus interfaces definitions into daemon package Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 05/17] gst-plugins-base: add support for non-X11-enabled distros Dmitry Eremin-Solenikov
2011-09-21 19:19 ` Koen Kooi
2011-09-21 18:39 ` [PATCH 06/17] libgpg-error: drop common-lisp files Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 07/17] gtk+: packaging fixups Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 08/17] polkit: fixup packaging Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 09/17] dbus-glib: disable bash-completion Dmitry Eremin-Solenikov
2011-09-21 19:19 ` Koen Kooi
2011-09-21 19:57 ` Dmitry Eremin-Solenikov
2011-09-21 20:00 ` Koen Kooi
2011-09-21 18:39 ` [PATCH 10/17] gettext: shut up unshipped files warning Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 11/17] eglibc: fix packaging of some of nativesdk packages Dmitry Eremin-Solenikov
2011-09-21 18:39 ` [PATCH 12/17] glib-2.0: include glib-gettextize stuff Dmitry Eremin-Solenikov
2011-09-21 18:40 ` [PATCH 13/17] libxml2: reinclude a -staticdev package Dmitry Eremin-Solenikov
2011-09-21 18:40 ` [PATCH 14/17] e2fsprogs: include devtools scripts Dmitry Eremin-Solenikov
2011-09-21 18:40 ` [PATCH 15/17] gcc: include plugin-related headers into packaged SDK Dmitry Eremin-Solenikov
2011-09-21 18:40 ` [PATCH 16/17] gcc: fix possible problems with nscd compilation during eglibc-nativesdk build Dmitry Eremin-Solenikov
2011-09-22 5:44 ` [PATCH 16s, Richard17] " Richard Purdie
2011-09-21 18:40 ` [PATCH 17/17] package.bbclass: make unshipped files a fatal error Dmitry Eremin-Solenikov
2011-09-22 5:48 ` Richard Purdie
2011-09-22 6:36 ` Dmitry Eremin-Solenikov
2011-09-22 9:45 ` Paul Eggleton
2011-09-22 9:50 ` Dmitry Eremin-Solenikov [this message]
2011-09-22 6:06 ` [PATCH 01/17] icecc-create-env: rename to -native Richard Purdie
2011-09-22 6:47 ` Dmitry Eremin-Solenikov
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=4E7B04E7.1000204@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=public-dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@lo.gmane.org \
--cc=public-paul.eggleton-VuQAYsv1563Yd54FQh9/CA@lo.gmane.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