From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org, Phil Blundell <pb@pbcl.net>
Subject: Re: [PATCH] insane.bbclass: Add missing R* variables to pkgvarcheck
Date: Thu, 02 May 2013 11:36:40 +0100 [thread overview]
Message-ID: <1572577.Dfl22j8Qhu@helios> (raw)
In-Reply-To: <1367489790.14512.235.camel@phil-desktop.brightsign>
On Thursday 02 May 2013 11:16:30 Phil Blundell wrote:
> On Wed, 2013-02-06 at 14:25 +0100, Martin Jansa wrote:
> > * check also RSUGGESTS, RCONFLICTS, RPROVIDES, RREPLACES
>
> These are already checked by recipe_sanity.bbclass. There's probably no
> need to check them again here.
recipe_sanity.bbclass doesn't get used by default - I guess you are enabling
it explicitly? I wonder if we should either (a) move all the recipe checks to
recipe_sanity.bbclass and enable it by default, or (b) move any currently
there and not covered by insane.bbclass to insane.bbclass and delete
recipe_sanity.bbclass.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-05-02 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 13:25 [PATCH] insane.bbclass: Add missing R* variables to pkgvarcheck Martin Jansa
2013-05-02 10:16 ` Phil Blundell
2013-05-02 10:36 ` Paul Eggleton [this message]
2013-05-02 10:59 ` Phil Blundell
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=1572577.Dfl22j8Qhu@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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