From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] remove unneeded python2 recipes
Date: Tue, 24 May 2016 08:20:13 +0100 [thread overview]
Message-ID: <1464074413.9570.32.camel@linuxfoundation.org> (raw)
In-Reply-To: <1700462.EZHnc1sg49@peggleto-mobl.ger.corp.intel.com>
On Tue, 2016-05-24 at 15:53 +1200, Paul Eggleton wrote:
> I had missed that change; that puts us into a bit of an interesting
> situation.
> buildtools-tarball is provided in order to support bitbake builds on
> hosts
> that don't have the required tools, but the changes required to
> support python
> 3 in the build system itself haven't been merged to master yet. So
> unless I'm
> missing something at the moment have a version of buildtools that
> doesn't
> actually support running the build system?
Its a chicken and egg problem in that we have autobuilders which don't
have python3 of the right version. Rather than build a special version
of the tarball from a branch, I merged this patch set on the basis that
anyone needing a python2 tarball could easily us the version from
before the patches merged and that we would be moving to python3 soon
everywhere.
Cheers,
Richard
next prev parent reply other threads:[~2016-05-24 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 3:25 [PATCH 0/6] remove unneeded python2 recipes Robert Yang
2016-05-24 3:25 ` [PATCH 1/6] packagegroup-self-hosted.bb: python-git -> python3-git Robert Yang
2016-05-24 3:25 ` [PATCH 2/6] python-pexpect: remove it Robert Yang
2016-05-24 3:25 ` [PATCH 3/6] python-async: " Robert Yang
2016-05-24 3:25 ` [PATCH 4/6] python-smmap: " Robert Yang
2016-05-24 3:25 ` [PATCH 5/6] python-gitdb: " Robert Yang
2016-05-24 3:25 ` [PATCH 6/6] python-git: " Robert Yang
2016-05-24 3:34 ` [PATCH 0/6] remove unneeded python2 recipes Paul Eggleton
2016-05-24 3:38 ` Robert Yang
2016-05-24 3:53 ` Paul Eggleton
2016-05-24 5:43 ` Robert Yang
2016-05-24 7:20 ` Richard Purdie [this message]
2016-05-24 18:06 ` Anders Darander
2016-05-25 1:18 ` Robert Yang
2016-05-25 12:48 ` alexander.kanavin
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=1464074413.9570.32.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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