From: Marek Vasut <marex@denx.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: koen@dominion.thruhere.net, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] nativesdk-packagegroup-python: buildtools-tarball: Introduce NativeSDK package group
Date: Fri, 19 Sep 2014 09:06:30 +0200 [thread overview]
Message-ID: <201409190906.30763.marex@denx.de> (raw)
In-Reply-To: <1411047011.4736.0.camel@ted>
On Thursday, September 18, 2014 at 03:30:11 PM, Richard Purdie wrote:
> On Thu, 2014-09-18 at 11:15 +0200, Marek Vasut wrote:
> > Introduce and use nativesdk-packagegroup-python , which contains all
> > necessary python components for the native SDK. Make use of this
> > package group in buildtools-tarball.bb immediatelly.
>
> Specifically, isn't this the list of packages needed to run bitbake and
> its associated utils? "python" isn't therefore a particularly good
> description of this package?
This is really just and only python packages, nothing else.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-09-19 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 9:15 [PATCH 1/2] nativesdk-packagegroup-python: buildtools-tarball: Introduce NativeSDK package group Marek Vasut
2014-09-18 9:15 ` [PATCH 2/2] meta-toolchain-qt: Install full set of python modules in Qt SDK toolchain Marek Vasut
2014-09-18 13:30 ` [PATCH 1/2] nativesdk-packagegroup-python: buildtools-tarball: Introduce NativeSDK package group Richard Purdie
2014-09-19 7:06 ` Marek Vasut [this message]
2014-09-19 16:13 ` Christopher Larson
2014-09-19 16:27 ` Marek Vasut
2014-09-19 16:42 ` Paul Eggleton
2014-09-19 16:52 ` Marek Vasut
2014-09-19 17:02 ` Christopher Larson
2014-09-19 17:08 ` 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=201409190906.30763.marex@denx.de \
--to=marex@denx.de \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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