From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] recipes: conform to OE packaging guidelines with RDEPENDS/RREDEPENDS
Date: Wed, 2 Jun 2010 19:43:45 +0200 [thread overview]
Message-ID: <20100602174345.GG16035@jama> (raw)
In-Reply-To: <20100602172058.GA26560@denix.org>
On Wed, Jun 02, 2010 at 01:20:58PM -0400, Denys Dmytriyenko wrote:
> Martin,
>
> > [PATCH] recipes: conform to OE packaging guidelines with RDEPENDS/RREDEPENDS
>
> Did you mean RRECOMMENDS instead of RREDEPENDS? :)
Yeah sure.. sorry for typo, thanks for spotting it, fixed before
pushing.
> Can you also please link to the mentioned OE packaging guidelines? Thanks.
Trying to find it, but even OE manual seems a bit inconsistent :/. Maybe
Koen has it as I just reused his commit message from
bf5e17fdbcefaa8ed34dceb25dc0becd6426fb6b
The point is that usually you want that RRECOMMENDS/RDEPENDS only for
${PN} and not ie for ${PN}-dev.
It's also checked in recipe-sanity.bbclass.
__recipe_sanity_badruntimevars = "RDEPENDS RPROVIDES RRECOMMENDS RCONFLICTS"
Regards,
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
next prev parent reply other threads:[~2010-06-02 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 13:39 [PATCH] recipes: conform to OE packaging guidelines with RDEPENDS/RREDEPENDS Martin Jansa
2010-06-02 17:16 ` Koen Kooi
2010-06-02 17:20 ` Denys Dmytriyenko
2010-06-02 17:43 ` Martin Jansa [this message]
2010-06-27 20:06 ` Paul Eggleton
2010-06-27 20:32 ` Martin Jansa
2010-06-27 21:57 ` Phil Blundell
2010-06-27 22:17 ` Martin Jansa
2010-06-27 22:17 ` [PATCH] opie-taskbar-images: fix RPROVIDES Martin Jansa
2010-06-28 21:27 ` Andrea Adami
2010-06-28 21:55 ` Paul Eggleton
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=20100602174345.GG16035@jama \
--to=martin.jansa@gmail.com \
--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