From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>, <ross.burton@intel.com>
Cc: paul.eggleton@linux.intel.com
Subject: [PATCH 0/2] distutils/setuptools:fix recipes may try to fetch code during do_compile
Date: Mon, 16 Jul 2018 23:34:29 -0400 [thread overview]
Message-ID: <cover.1531798346.git.hongxu.jia@windriver.com> (raw)
The following changes since commit 05c32d2de1ee4681cc78cb107a158e9ab22c9619:
oeqa/selftest/wic: Split tests into two class groups (2018-07-16 13:21:35 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib hongxu/setuptools-fetch
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=hongxu/setuptools-fetch
Hongxu Jia (2):
distutils/setuptools-native: do not try to fetch code during
do_compile
distutils3/setuptools3-native: do not try to fetch code during
do_compile
meta/classes/distutils.bbclass | 2 ++
meta/classes/distutils3.bbclass | 2 ++
...ionally-do-not-fetch-code-by-easy_install.patch | 35 ++++++++++++++++++++++
.../python/python-setuptools_40.0.0.bb | 2 ++
...ionally-do-not-fetch-code-by-easy_install.patch | 35 ++++++++++++++++++++++
.../python/python3-setuptools_40.0.0.bb | 2 ++
6 files changed, 78 insertions(+)
create mode 100644 meta/recipes-devtools/python/python-setuptools/0001-conditionally-do-not-fetch-code-by-easy_install.patch
create mode 100644 meta/recipes-devtools/python/python3-setuptools/0001-conditionally-do-not-fetch-code-by-easy_install.patch
--
2.8.1
next reply other threads:[~2018-07-17 3:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 3:34 Hongxu Jia [this message]
2018-07-17 3:34 ` [PATCH 1/2] distutils/setuptools-native: do not try to fetch code during do_compile Hongxu Jia
2018-07-17 3:34 ` [PATCH 2/2] distutils3/setuptools3-native: " Hongxu Jia
2018-07-17 11:13 ` Burton, Ross
2018-07-17 13:36 ` [PATCH V2] distutils/setuptools-native, " Hongxu Jia
2018-07-27 11:38 ` Martin Jansa
2018-07-27 11:41 ` Derek Straka
2018-07-27 12:43 ` Derek Straka
2018-07-27 13:29 ` Martin Jansa
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.1531798346.git.hongxu.jia@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@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