From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: should all RDEPENDS always have an attached package name?
Date: Mon, 11 Aug 2014 14:23:37 +0100 [thread overview]
Message-ID: <1407763417.22187.12.camel@ted> (raw)
In-Reply-To: <alpine.LFD.2.11.1408110909060.11035@localhost>
On Mon, 2014-08-11 at 09:11 -0400, Robert P. J. Day wrote:
> according to yocto ref manual, all uses of RDEPENDS should be
> suffixed with a package name (normally, _${PN}, of course), but i just
> noticed that the buildtools-tarball.bb recipe file contains:
>
> RDEPENDS = "${TOOLCHAIN_HOST_TASK}"
>
> i suspect that still works just fine, but it does disagree with the
> rather adamant admonition in the ref manual.
The buildtools-tarball doesn't have any packages so in this particular
case, it is acceptable (and accepted by bitbake and the QA tests).
Cheers,
Richard
next prev parent reply other threads:[~2014-08-11 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 13:11 should all RDEPENDS always have an attached package name? Robert P. J. Day
2014-08-11 13:23 ` Richard Purdie [this message]
2014-08-11 13:24 ` Robert P. J. Day
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=1407763417.22187.12.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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