Commit Graph

5 Commits

Author SHA1 Message Date
Alexandru Ardelean ee2a4278d9 python-cffi: bump to version 1.15.0
And use AUTORELEASE for PKG_RELEASE.

Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2021-10-19 13:22:25 -07:00
Alexandru Ardelean e08b94b753 python-cffi: bump to version 1.14.6
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
2021-07-14 11:20:07 +03:00
Jeffery To 4aba039a2d
python-cffi: Update to 1.14.5
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2021-02-15 05:35:23 +08:00
Jeffery To c8326f7140 python-cffi: Update to 1.14.4
Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2020-12-01 11:25:01 +02:00
Jeffery To 722a5b8efa
python3: Use hash-checking mode when installing host pip packages
In hash-checking mode[1], pip will verify downloaded package archives
(source tarballs in our case) against known SHA256 hashes before
installing the packages.

As a consequence, this requires the use of requirements files[2] and
pinning packages to known versions.

The syntax for package Makefiles has changed slightly;
HOST_PYTHON3_PACKAGE_BUILD_DEPENDS no longer accepts requirement
specifiers like "foo>=1.0", only requirements file names (which are the
same as package names in the most common case).

This also updates affected packages, in particular:

* python-zipp: "setuptools_scm[toml]" has been split into
  "setuptools-scm toml" to reuse the requirements file for
  setuptools-scm (the extra depends installed by "setuptools_scm[toml]"
  is toml).

* python-pycparser: This previously used ply 3.10, whereas the
  requirements file will now install 3.11.

[1]: https://pip.pypa.io/en/stable/reference/pip_install/#hash-checking-mode
[2]: https://pip.pypa.io/en/stable/user_guide/#requirements-files

Signed-off-by: Jeffery To <jeffery.to@gmail.com>
2020-08-17 23:05:49 +08:00