All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chong Lu <Chong.Lu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3] oelint.bbclass: make oelint bbclass work
Date: Fri, 1 Aug 2014 15:15:05 +0800	[thread overview]
Message-ID: <cover.1406876955.git.Chong.Lu@windriver.com> (raw)

In conf/local.conf, add 'INHERIT += "oelint"' to test.
We can get many warnings, like following:

WARNING: diffutils: HOMEPAGE is not set
WARNING: sed: DESCRIPTION is not set
WARNING: perl: DESCRIPTION is not set
WARNING: perl: debian/cpan_definstalldirs.diff doesn't have Signed-off-by
WARNING: perl: debian/cpan_definstalldirs.diff doesn't have Upstream-Status

The following changes since commit 2d1660112e54653f7bb763939d0416472c49fe01:

  populate_sdk_base: Fix grep command usage on old hosts (2014-07-29 09:58:27 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib chonglu/oelint
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=chonglu/oelint

Chong Lu (3):
  oelint.bbclass: make oelint bbclass work
  oelint.bbclass: add patch checking
  oelint.bbclass: Check for ${PN} or ${P} usage

 meta/classes/oelint.bbclass | 251 ++++++++++++++------------------------------
 1 file changed, 81 insertions(+), 170 deletions(-)

-- 
1.9.1



             reply	other threads:[~2014-08-01  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01  7:15 Chong Lu [this message]
2014-08-01  7:15 ` [PATCH 1/3] oelint.bbclass: make oelint bbclass work Chong Lu
2014-08-01  7:15 ` [PATCH 2/3] oelint.bbclass: add patch checking Chong Lu
2014-08-01  7:15 ` [PATCH 3/3] oelint.bbclass: Check for ${PN} or ${P} usage Chong Lu
2014-08-01  7:37   ` Robert P. J. Day
2014-08-01  7:57     ` Chong Lu

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.1406876955.git.Chong.Lu@windriver.com \
    --to=chong.lu@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.