Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] insane.bbclass: add missing QA to WARN_QA
Date: Thu, 19 Mar 2015 17:50:39 +0800	[thread overview]
Message-ID: <550A9BEF.7070802@windriver.com> (raw)
In-Reply-To: <1854796.UtEVgRut4l@peggleto-mobl.ger.corp.intel.com>


Hi Paul,

Thanks for the reply, I just wanted to add them to ALL_QA, but you
are right, I need do more checking and fix, please ignore this patch atm.

// Robert

On 03/19/2015 05:37 PM, Paul Eggleton wrote:
> Hi Robert,
>
> On Thursday 19 March 2015 02:17:43 Robert Yang wrote:
>> The following QA were not in WARN_QA or ERROR_QA, so they are not in
>> ALL_QA:
>>
>> buildpaths
>
> Last I checked enabling this throws up quite a few issues, some of which
> aren't a problem. Has that been fixed? If not, we can't enable it.
>
>> desktop
>
> I'm pretty sure we kept this one off deliberately as well, there are too many
> bad desktop files out there and for most people it doesn't matter.
>
>> libexec
>
> Does this test work?
>
>> pkgname
>
> Only certain package managers care about the rules this test enforces.
>
>> symlink-to-sysroot
>
> I agree this one should probably be enabled.
>
>> unsafe-references-in-binaries
>> unsafe-references-in-scripts
>
> We haven't enabled these because there isn't general agreement that this is a
> problem for everyone.
>
> Cheers,
> Paul
>


      reply	other threads:[~2015-03-19  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  9:17 [PATCH 0/1] insane.bbclass: add missing QA to WARN_QA Robert Yang
2015-03-19  9:17 ` [PATCH 1/1] " Robert Yang
2015-03-19  9:37   ` Paul Eggleton
2015-03-19  9:50     ` Robert Yang [this message]

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=550A9BEF.7070802@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox