Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <kai.kang@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [RFC PATCH 0/1] Split do_package_qa in insane.bbclass to be a new task
Date: Mon, 11 Mar 2013 11:31:16 +0800	[thread overview]
Message-ID: <cover.1362966448.git.kai.kang@windriver.com> (raw)

Hi Richard,

This patch is try to accomplish Yocto #3190, and you said:

"
The sanity tests in insane.bbclass need refactoring to make it easier to extend.
In particular, some packaging tests are currently ending up in package.bbclass.
These should be in insane.bbclass with hooks added as appropriate.

Further, all tests should honour the settings of QA_WARN and QA_ERROR.
"

do_package_qa is splitted as a new task run after do_package. Then 'inherit package'
could be removed from insane.bbclass, and do_package_qa doesn't end in package.bbclass.

I know this patch is not enough for this feature, but I want to make sure this is the 
right direction and hope to receive more guidance.

Would you like to give more guidance?

Thanks a lot.

Regards,
Kai


The following changes since commit 93ec7b4d1550e07caec86e2998d0f94a01c7e785:

  xserver-xf86-config: atom-pc doesn't need a xorg.conf (2013-03-04 14:42:11 +0000)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib kangkai/insane
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/insane

Kang Kai (1):
  insane.bbclass: make do_package_qa be a task

 meta/classes/insane.bbclass |   15 +++++++++++++--
 1 files changed, 13 insertions(+), 2 deletions(-)

-- 
1.7.5.4




             reply	other threads:[~2013-03-11  3:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11  3:31 Kang Kai [this message]
2013-03-11  3:31 ` [PATCH 1/1] insane.bbclass: make do_package_qa be a task Kang Kai
2013-03-11  8:06   ` Bernhard Reutner-Fischer
2013-03-11  8:24     ` Kang Kai

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=cover.1362966448.git.kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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