All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Orling <timothy.t.orling@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Move SCons to Python 3
Date: Fri,  7 Jun 2019 16:47:50 -0700	[thread overview]
Message-ID: <cover.1559950879.git.timothy.t.orling@linux.intel.com> (raw)

python-scons and python-scons-native are perhaps the last python2 only
recipes in oe-core. With Python 2 going EOL in or before 2020, it's time
to switch everything to Python 3.

I updated scons.bbclass to use python3-scons-native. Tested build with serf.

I also added a simple oeqa/runtime test while I was at it.

I did not drop python-scons and python-scons-native, although we should
at some point soon.

[YOCTO #13381]

The following changes since commit 666f6192aaa9e847ad0d920a487b82d984b58d26:

  gnutls: Use the sysconfdir variable for the ca-certificates path (2019-06-07 09:10:34 +0100)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib timo/python3-scons
  http://cgit.openembedded.org//log/?h=timo/python3-scons

Tim Orling (4):
  python3-scons-{native}: add recipe for v3.0.5
  scons.bbclass: use python3-scons
  serf: switch to python3-scons-native
  oeqa/runtime: add simple test for scons

 meta/classes/scons.bbclass                    |  2 +-
 meta/conf/distro/include/maintainers.inc      |  2 +
 meta/lib/oeqa/runtime/cases/scons.py          | 37 +++++++++++++++++++
 meta/lib/oeqa/runtime/files/SConstruct        |  1 +
 meta/lib/oeqa/runtime/files/hello.c           |  5 +++
 .../python/python3-scons-native_3.0.5.bb      |  8 ++++
 .../python/python3-scons_3.0.5.bb             | 29 +++++++++++++++
 meta/recipes-support/serf/serf_1.3.9.bb       |  2 +-
 8 files changed, 84 insertions(+), 2 deletions(-)
 create mode 100644 meta/lib/oeqa/runtime/cases/scons.py
 create mode 100644 meta/lib/oeqa/runtime/files/SConstruct
 create mode 100644 meta/lib/oeqa/runtime/files/hello.c
 create mode 100644 meta/recipes-devtools/python/python3-scons-native_3.0.5.bb
 create mode 100644 meta/recipes-devtools/python/python3-scons_3.0.5.bb

-- 
2.20.1



             reply	other threads:[~2019-06-07 23:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 23:47 Tim Orling [this message]
2019-06-07 23:47 ` [PATCH 1/4] python3-scons-{native}: add recipe for v3.0.5 Tim Orling
2019-06-08  0:56   ` Tim Orling
2019-06-07 23:47 ` [PATCH 2/4] scons.bbclass: use python3-scons Tim Orling
2019-06-20 13:36   ` Khem Raj
2019-06-21  0:18     ` Tim Orling
2019-06-21  3:27       ` Khem Raj
2019-06-22  8:58         ` Adrian Bunk
2019-06-23  0:03           ` Khem Raj
2019-06-23 16:44             ` Tim Orling
2019-06-23 19:24               ` Adrian Bunk
2019-06-24  1:49                 ` Tim Orling
2019-06-24  2:41       ` Alistair Francis
2019-06-24  8:20         ` Adrian Bunk
2019-06-24 17:27           ` Alistair Francis
2019-06-07 23:47 ` [PATCH 3/4] serf: switch to python3-scons-native Tim Orling
2019-06-10  5:10   ` Mittal, Anuj
2019-06-10  5:22     ` Tim Orling
2019-06-12 20:52     ` Khem Raj
2019-06-07 23:47 ` [PATCH 4/4] oeqa/runtime: add simple test for scons Tim Orling
2019-06-08  3:54 ` ✗ patchtest: failure for Move SCons to Python 3 Patchwork
2019-06-08  4:04   ` Tim Orling
2019-06-08  7:13 ` [PATCH 0/4] " Burton, Ross

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.1559950879.git.timothy.t.orling@linux.intel.com \
    --to=timothy.t.orling@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.