From: Jonathan Liu <net147@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-qt5][PATCH 2/2] README: remove meta-ruby dependency
Date: Tue, 15 Dec 2015 20:44:29 +1100 [thread overview]
Message-ID: <1450172669-20882-2-git-send-email-net147@gmail.com> (raw)
In-Reply-To: <1450172669-20882-1-git-send-email-net147@gmail.com>
The ruby recipe has been moved into OE-core so the meta-ruby layer
is no longer needed as the ruby recipe will always be present.
Signed-off-by: Jonathan Liu <net147@gmail.com>
---
README | 5 -----
1 file changed, 5 deletions(-)
diff --git a/README b/README
index dcfb5e5..9817851 100644
--- a/README
+++ b/README
@@ -4,11 +4,6 @@ URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD
-URI: git://github.com/openembedded/meta-oe.git
-layers: meta-ruby
-branch: master
-revision: HEAD
-
When building stuff like qtdeclarative, qtquick, qtwebkit, make sure that
you have required PACKAGECONFIG options enabled in qtbase build, see qtbase.inc
for detail.
--
2.6.4
prev parent reply other threads:[~2015-12-15 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 9:44 [meta-qt5][PATCH 1/2] packagegroup-qt5-toolchain-target: do not check for meta-ruby layer Jonathan Liu
2015-12-15 9:44 ` Jonathan Liu [this message]
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=1450172669-20882-2-git-send-email-net147@gmail.com \
--to=net147@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