From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/6] buildtools-tarball: add python-git
Date: Fri, 28 Jun 2013 17:19:06 +0100 [thread overview]
Message-ID: <26f1725c369f1c6f5bd19ed439e464128aca803e.1372436217.git.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <cover.1372436217.git.paul.eggleton@linux.intel.com>
In-Reply-To: <cover.1372436217.git.paul.eggleton@linux.intel.com>
python-git is needed by buildhistory-diff and the OE layer index update
script, and on machines where buildtools-tarball is necessary given we
are providing python we must provide this module as well.
Fixes [YOCTO #4747].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
meta/recipes-core/meta/buildtools-tarball.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/meta/buildtools-tarball.bb b/meta/recipes-core/meta/buildtools-tarball.bb
index 8b68f71..e8abc06 100644
--- a/meta/recipes-core/meta/buildtools-tarball.bb
+++ b/meta/recipes-core/meta/buildtools-tarball.bb
@@ -32,6 +32,7 @@ TOOLCHAIN_HOST_TASK ?= "\
nativesdk-python-unittest \
nativesdk-python-difflib \
nativesdk-python-pprint \
+ nativesdk-python-git \
nativesdk-ncurses-terminfo-base \
nativesdk-chrpath \
nativesdk-tar \
--
1.8.1.2
next prev parent reply other threads:[~2013-06-28 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:19 [PATCH 0/6] Add python-git module Paul Eggleton
2013-06-28 16:19 ` [PATCH 1/6] python-async: add recipe Paul Eggleton
2013-06-28 16:19 ` [PATCH 2/6] python-smmap: " Paul Eggleton
2013-06-28 16:19 ` [PATCH 3/6] python-gitdb: " Paul Eggleton
2013-06-28 16:19 ` [PATCH 4/6] python-git: " Paul Eggleton
2013-06-28 16:19 ` Paul Eggleton [this message]
2013-06-28 16:19 ` [PATCH 6/6] packagegroup-self-hosted: add python-git 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=26f1725c369f1c6f5bd19ed439e464128aca803e.1372436217.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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