Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 6/8] p910nd: add 0.95 version
Date: Sun, 08 May 2011 10:31:32 +0200	[thread overview]
Message-ID: <iq5kd4$gie$1@dough.gmane.org> (raw)
In-Reply-To: <1304837421.4124.11.camel@mattotaupa>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-05-11 08:50, Paul Menzel wrote:
> Am Sonntag, den 08.05.2011, 03:02 +0200 schrieb Koen Kooi:
> 
> […]
> 
>>> +DESCRIPTION = "A small network printer daemon for embedded situations that passes the job directly to the printer."
>>> +SECTION = "console/utils"
> 
> This should be dropped, since it is redundant.
> 
>>> +HOMEPAGE = "http://p910nd.sourceforge.net/"
>>> +SECTION = "console/utils"
> 
> This is the correct location according to the style guide [1].
> 
>>> +RDEPENDS_${PN}-avahi = "avahi"
>>
>> Again, RDEPENDS go below do_install
> 
> When was this agreed on? The style guide says differently.

They go in the recipe the order they are used, so:

info (HOMEPAGE, DESCRIPTION, etc)
configure
compile
install
package

RDEPENDS/RRECOMMENDS/FILES/PACKAGES are all for packaging, so they are
grouped.

Have a look at the p910nd recipe, then you see why grouping them is best.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNxlTkMkyGM64RGpERArwnAKCS7EAMDfaLEUF+ucnrDx2skvQVrQCeOzUh
gJn1V8apsWuW68YCpECbaRA=
=H8n/
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-05-08  8:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-07 19:19 [meta-oe] Pull request for misc changes Otavio Salvador
2011-05-07 19:59 ` Koen Kooi
2011-05-07 22:11 ` [meta-oe][PATCH 1/8] fuse: add 2.8.5 Otavio Salvador
2011-05-07 22:11   ` [meta-oe][PATCH 2/8] ntfs-3g-ntfsprogs: add 2011.4.12 recipes Otavio Salvador
2011-05-07 22:11     ` [meta-oe][PATCH 3/8] setxkbmap: add 1.2.0 version Otavio Salvador
2011-05-07 22:11       ` [meta-oe][PATCH 4/8] freerdp: add recipe based on GIT from 2009-03-29 Otavio Salvador
2011-05-07 22:11         ` [meta-oe][PATCH 5/8] pixman.inc: use Xorg mirror Otavio Salvador
2011-05-07 22:11           ` [meta-oe][PATCH 6/8] p910nd: add 0.95 version Otavio Salvador
2011-05-07 22:11             ` [meta-oe][PATCH 7/8] libiconv: drop hack since gettext was being inherited Otavio Salvador
2011-05-07 22:11               ` [meta-oe][PATCH 8/8] libinih: add git recipe Otavio Salvador
2011-05-08  1:03                 ` Koen Kooi
2011-05-08  2:30                   ` Otavio Salvador
2011-05-08  1:02             ` [meta-oe][PATCH 6/8] p910nd: add 0.95 version Koen Kooi
2011-05-08  2:38               ` Otavio Salvador
2011-05-08  6:50               ` Paul Menzel
2011-05-08  8:31                 ` Koen Kooi [this message]
2011-05-08  1:00         ` [meta-oe][PATCH 4/8] freerdp: add recipe based on GIT from 2009-03-29 Koen Kooi
2011-05-08  0:59     ` [meta-oe][PATCH 2/8] ntfs-3g-ntfsprogs: add 2011.4.12 recipes Koen Kooi
2011-05-09 19:31 ` [meta-oe] Pull request for misc changes Koen Kooi
2011-05-09 19:48   ` Otavio Salvador
2011-05-09 20:19     ` Koen Kooi

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='iq5kd4$gie$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@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