From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] [RESEND]Create a script for SUMMARY audit in recipes
Date: Thu, 22 Dec 2011 10:17:43 +0000 [thread overview]
Message-ID: <1965049.NZCOpGhGnY@helios> (raw)
In-Reply-To: <4EF22C79.7080906@windriver.com>
On Wednesday 21 December 2011 12:59:05 Mark Hatle wrote:
> On 12/21/11 12:43 PM, Saul Wold wrote:
> > Which is why I think this issue is cropping up. So, then the proposal
> > should really be to add SUMMARY to all recipes and initially make it a
> > warning for now if non-existent SUMMARY as with DESCRIPTION and then
> > remove the existing SUMMARY = ${PN}-${PV} ...??
> >
> > The audit would then be the list of warnings which later becomes error
>
> I agree, this should become some kind of an audit warning, so we can improve
> the quality of the recipe information. I'm not sure I want it to be an
> error though as it may impact folks with existing OE recipes...
Do we want to be showing this warning to everyone or should it just be part of
a class you can enable (e.g. oelint.bbclass - which needs some work by the
looks of it)?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-12-22 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 4:32 [PATCH 0/1] [RESEND]Create a script for SUMMARY audit in recipes Shane Wang
2011-12-21 4:32 ` [PATCH 1/1] Create " Shane Wang
2011-12-21 5:45 ` [PATCH 0/1] [RESEND]Create " Saul Wold
2011-12-21 6:10 ` Wang, Shane
2011-12-21 18:16 ` Joshua Lock
2011-12-21 18:43 ` Saul Wold
2011-12-21 18:59 ` Mark Hatle
2011-12-22 10:17 ` Paul Eggleton [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=1965049.NZCOpGhGnY@helios \
--to=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox