buildroot/package/python-setuptools, branch 2019.02-op-build

package/python-setuptools: add comment about python3-setuptools

2019-01-16T09:42:10+00:00

As suggested by Arnout, add a comment to indicate that the version of python-setuptools must be kept in sync with python3-setuptools. Suggested-by: Arnout Vandecappelle Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

package/pkg-python: use host-python3-setuptools when needed

2019-01-01T10:16:10+00:00

When a package uses "setuptools" as its _SETUP_TYPE, we currently add a dependency on host-python-setuptools. This means that: (1) When BR2_PACKAGE_PYTHON=y, the default host Python version is Python 2.x, and host-python-setuptools is installed for host-python. (2) When BR2_PACKAGE_PYTHON3=y, the default host Python version is Python 3.x, and host-python-setuptools is installed for host-python3. (3) When no target Python interpreter is selected, the default host Python version is Python 2.x, and host-python-setuptools is installed for host-python. Situations (1) and (3) are problematic for host Python packages that need Python 3.x. Such packages use _NEEDS_HOST_PYTHON = python3, but if they use setuptools as their setup type, they will not find setuptools installed for host-python3 in situations (1) and (3) described above. We currently have a single package that sets _NEEDS_HOST_PYTHON = python3: host-meson. host-meson generally works because if setuptools is not found, it falls back to distutils, which is part of the standard Python library. However, if there is a setuptools version installed system-wide, it may be picked up, but may not necessarily be the same version as Buildroot setuptools, potentially causing problems. This commit makes the necessary change to the python-package infrastructure to fix this behavior, by identifying the following cases: - When a host Python package says _NEEDS_HOST_PYTHON = python3, then we know it wants setuptools installed for host-python3, so we use host-python3-setuptools. - When a host Python package says _NEEDS_HOST_PYTHON = python2, then we known it wants setuptools installed for host-python, so we use host-python-setuptools. - When BR2_PACKAGE_PYTHON3=y, and we have a target package, or a host package with no NEEDS_HOST_PYTHON option, then we want setuptools installed for host-python3, so we use host-python3-setuptools. - When BR2_PACKAGE_PYTHON=y or no target interpreter is enabled at all, and we have a target package, or a host package with no NEEDS_HOST_PYTHON option, then we want setuptools for host-python, so we use host-python-setuptools. To make this happen, we use host-python3-setuptools introduced in a previous commit, but we also change host-python-setuptools to force its installation for host-python. The latter is needed if you build with BR2_PACKAGE_PYTHON3=y but want to install a Python-based package that has NEEDS_HOST_PYTHON=python2. There is one single package that needs be adjusted following this: lirc-tools, because it is not using the python-package infrastructure. It directly depends on host-python-setuptools, which no longer works because host-python-setuptools now only installs for Python 2.x, while lirc-tools Python binding only supports Python 3.x. Switching to host-python3-setuptools solves this problem. Signed-off-by: Thomas Petazzoni Reviewed-by: Asaf Kahlon Reviewed-by: Yegor Yefremov Signed-off-by: Thomas Petazzoni

python-setuptools: bump to version 40.6.3

2018-12-14T20:29:31+00:00

Signed-off-by: Asaf Kahlon Signed-off-by: Peter Korsgaard

python-setuptools: bump to version 40.6.2

2018-11-16T22:26:22+00:00

Signed-off-by: Asaf Kahlon Signed-off-by: Peter Korsgaard

python-setuptools: bump to version 40.5.0

2018-10-28T07:11:07+00:00

Signed-off-by: Asaf Kahlon Signed-off-by: Peter Korsgaard

python-setuptools: use pypi package

2018-09-22T16:50:23+00:00

The releases on Github produces a setuptools version that isn't PEP518 compliant because a .post number is attached to the .egg file (IE: 40.0.0.post20180820) which can cause a python package using setuptools to fail if looking for a setuptools version. Instead, using the official release from pypi is recommended as it does not produce a .post version on the egg file. Another benefit is not having to run bootstrap.py either. See https://github.com/pypa/setuptools/issues/1462 for more details about the issue Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

python-setuptools: bump to 40.0.0

2018-08-20T20:26:27+00:00

With the introduction of Python 3.7.0, setuptools also needs to be updated. Without the update, several packages will fail to build or install with a ValueError: bad marshal data (unknown type code). Updating setuptools to 40.0.0 version fixes this issue. Even though 40.1.0 is out, updating to 40.0.0 is recommended as it seems like 40.1.0 breaks version detection on some python packages such as python-cryptography which will error out with a complaint that setuptools is too old, even though it's at 40.1.0. Using 40.0.0 fixes the issue. Fixes: http://autobuild.buildroot.net/results/636/636da0febe02f991095965d52cc4a8b2da644777/ http://autobuild.buildroot.net/results/5f6/5f659130a6a32a4c43d6ed2c3b559df77ae18249/ Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

python-setuptools: bump to version v38.4.0

2018-01-16T22:49:15+00:00

Add licence checksum. Signed-off-by: Yegor Yefremov Signed-off-by: Thomas Petazzoni

package/*/Config.in: fix help text check-package warnings

2017-12-18T08:22:54+00:00

This commit fixes the warnings reported by check-package on the help text of all package Config.in files, related to the formatting of the help text: should start with a tab, then 2 spaces, then at most 62 characters. The vast majority of warnings fixed were caused by too long lines. A few warnings were related to spaces being used instead of a tab to indent the help text. Signed-off-by: Thomas Petazzoni

Globally replace $(HOST_DIR)/usr/bin with $(HOST_DIR)/bin

2017-07-05T13:19:29+00:00

Since things are no longer installed in $(HOST_DIR)/usr, the callers should also not refer to it. This is a mechanical change with git grep -l '$(HOST_DIR)/usr/bin' | xargs sed -i 's%$(HOST_DIR)/usr/bin%$(HOST_DIR)/bin%g' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni