From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] kernel.bbclass: add perl python bash to RDEPENDS_kernel-dev
Date: Tue, 15 Jul 2014 07:34:53 -0700 [thread overview]
Message-ID: <cover.1405434689.git.liezhi.yang@windriver.com> (raw)
Send this patch in another thread since it is special, added:
RDEPENDS_kernel-dev = "perl bash python"
Now the perl-dev, bash-dev and python-dev will also be pulled in since
kernel-dev is a dev package.
// Robert
The following changes since commit fa325e44f5b429b4038022b31285af9c94672943:
insane: Ensure do_package_qa happens after do_packagedata (2014-07-11 23:19:18 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib rbt/kernel-dev
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/kernel-dev
Robert Yang (1):
kernel.bbclass: add perl python bash to RDEPENDS_kernel-dev
meta/classes/kernel.bbclass | 1 +
1 file changed, 1 insertion(+)
--
1.7.9.5
next reply other threads:[~2014-07-15 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 14:34 Robert Yang [this message]
2014-07-15 14:34 ` [PATCH 1/1] kernel.bbclass: add perl python bash to RDEPENDS_kernel-dev Robert Yang
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=cover.1405434689.git.liezhi.yang@windriver.com \
--to=liezhi.yang@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