All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Request for Reviews and future package updates
Date: Fri, 19 Nov 2010 12:08:34 +0000	[thread overview]
Message-ID: <1290168514.1272.12249.camel@rex> (raw)
In-Reply-To: <4CE5A9EE.2080306@windriver.com>

On Thu, 2010-11-18 at 16:34 -0600, Mark Hatle wrote:
> I'd like to request that future reviews and package updates include "SUMMARY"
> information in the recipe files.
> 
> For people who are not aware of the issue, a policy was created in Yocto 0.9
> that we want each package to contain both a summary and description.  The
> summary should be short and fewer then 80 characters if possible.  While the
> description may be arbitrarily long and should explain the functionality of the
> package.
> 
> By default, the SUMMARY is set to equal the DESCRIPTION if it was not previously
> set.
> 
> So if the DESCRIPTION is short, a SUMMARY may not be required, such as:
> 
> DESCRIPTION = "A multi-purpose linux bootloader"
> 
> 
> However, in a package with a more complicated description, such as chrpath:
> 
> DESCRIPTION = "chrpath allows you to change the rpath (where the application \
> looks for libraries) in an application. It does not (yet) allow you to add an \
> rpath if there isn't one already."
> 
> A short summary should be added to the recipe:
> 
> SUMMARY = "Tool to edit rpath in ELF binaries"
> 
> ---
> 
> I'm currently going through Poky updating many of the recipes by updating
> descriptions as necessary and adding SUMMARY fields.  In the future, or as
> packages are updated, we should ensure that both the SUMMARY and DESCRIPTION are
> present and up-to-date.

It would be nice to have a section in the wiki with the minimum recipe
requirements documented. We certainly have some but I'm not sure
everything is written down in one place?

Cheers,

Richard



  reply	other threads:[~2010-11-19 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 22:34 Request for Reviews and future package updates Mark Hatle
2010-11-19 12:08 ` Richard Purdie [this message]
2010-11-19 16:39   ` Mark Hatle
2010-11-19 22:58   ` Darren Hart

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=1290168514.1272.12249.camel@rex \
    --to=rpurdie@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=yocto@yoctoproject.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.