Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] import recipe_sanity.bbclass from oe master
Date: Fri, 10 Jun 2011 10:09:16 -0500	[thread overview]
Message-ID: <4DF2339C.5000609@windriver.com> (raw)
In-Reply-To: <1307716082.25285.21.camel@phil-desktop>

On 6/10/11 9:28 AM, Phil Blundell wrote:
> This is a verbatim copy of the corresponding class from oe master.
> 
> Signed-off-by: Phil Blundell <philb@gnu.org>
> ---

One of the new features we have in oe-core (likely not well publicized) is
"SUMMARY" information.

If this patch goes in, we likely should check for the existence of a SUMMARY as
well.  Not all recipes have package summaries, but in the end they all should.

--Mark

> +__recipe_sanity_reqvars = "DESCRIPTION"
> +__recipe_sanity_reqdiffvars = "LICENSE"




      reply	other threads:[~2011-06-10 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-10 14:28 [PATCH] import recipe_sanity.bbclass from oe master Phil Blundell
2011-06-10 15:09 ` Mark Hatle [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=4DF2339C.5000609@windriver.com \
    --to=mark.hatle@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox