From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] python3: Bump version to 3.6.0
Date: Sun, 19 Mar 2017 15:53:14 +0100 [thread overview]
Message-ID: <20170319155314.3ca86764@free-electrons.com> (raw)
In-Reply-To: <20170314234228.3744-2-andrew.smirnov@gmail.com>
Hello,
On Tue, 14 Mar 2017 16:42:28 -0700, Andrey Smirnov wrote:
> python3: Bump version to 3.6.0
Thanks for this new version, with updated explanations. It's almost
ready, but I still have a few comments.
> +define PKG_PYTHON_SYSCONFIGDATA_NAME
> +$(shell basename $(shell find $(TARGET_DIR)/ -name "_sysconfigdata_m_linux_*.pyc" | head -n 1) .pyc)
> +endef
Could you replace this with:
+PKG_PYTHON_SYSCONFIGDATA_NAME = \
+ $(basename $(notdir $(wildcard $(STAGING_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)/_sysconfigdata_*.py)))
It does the same, but using make code.
To be honest, I find it really annoying that we have to do this to find
the name of the sysconfigdata package. I've thought about the following:
- Have the Python build system output somewhere the name of the
sysconfigdata module that has been generated.
- Compute the name of the sysconfigdata module: it's always going to be:
sysconfigdata_m_linux_<output of gcc -dumpmachine>
But well, your solution is as simple, so let's go for it.
> -Subject: [PATCH] setup.py: do not add invalid header locations
> +Subject: [PATCH 01/31] setup.py: do not add invalid header locations
Please generate patches with "git format-patch -N" to get rid of the
numbering, i.e to have [PATCH] instead of [PATCH 01/31].
> --- a/package/python3/0003-Make-the-build-of-pyc-files-conditional.patch
> +++ b/package/python3/0002-Make-the-build-of-pyc-files-conditional.patch
> @@ -1,22 +1,24 @@
> -From 5df8e9556e8026dd19cf932fa8f2b726f56182d1 Mon Sep 17 00:00:00 2001
> -From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> -Date: Wed, 23 Dec 2015 11:29:35 +0100
> -Subject: [PATCH] Make the build of pyc files conditional
> +From a3aedafc04a81c5a6406c60e82d072377fee0cd1 Mon Sep 17 00:00:00 2001
> +From: Andrey Smirnov <andrew.smirnov@gmail.com>
Why are all patches you have changed now re-assigned with your From?
You should preserve the authorship of the original author.
> # Provided to other packages
> -PYTHON3_PATH = $(TARGET_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)/sysconfigdata/:$(TARGET_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)/site-packages/
> +PYTHON3_PATH = $(TARGET_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)/:$(TARGET_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)/site-packages/
Why do we now need
$(TARGET_DIR)/usr/lib/python$(PYTHON3_VERSION_MAJOR)/ ?
Could you fix the above issues and submit a new version?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-19 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 23:42 [Buildroot] [PATCH v2 1/2] scripts/pycompile: Accomodate latest Python 3 codebase Andrey Smirnov
2017-03-14 23:42 ` [Buildroot] [PATCH v2 2/2] python3: Bump version to 3.6.0 Andrey Smirnov
2017-03-19 14:53 ` Thomas Petazzoni [this message]
2017-03-22 0:49 ` Andrey Smirnov
2017-03-22 7:56 ` Thomas Petazzoni
2017-03-19 14:53 ` [Buildroot] [PATCH v2 1/2] scripts/pycompile: Accomodate latest Python 3 codebase Thomas Petazzoni
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=20170319155314.3ca86764@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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