Versions
v99999999999999 :: 0 :: gentoo
- Modified
- License
- BSD
v20200512145953-r1 :: 0 :: gentoo
- Modified
- License
- BSD
- Keywords
- amd64 arm64 ppc64 x86 ~loong
USE flags
python_single_target
- python3_10
- Build for Python 3.10 only
- python3_11
- Build for Python 3.11 only
- python3_12
- Build for Python 3.12 only
- python3_13
- Build for Python 3.13 only
Runtime Dependencies
dev-lang / python : Freethreading (no-GIL) version of Python programming language
Change logs
- Repository mirror & CI · gentoo
Merge updates from master - Sam James · gentoo
dev-build/gyp: Stabilize 20200512145953-r1 arm64, #922248
Signed-off-by: Sam James <sam@gentoo.org> - Sam James · gentoo
dev-build/gyp: drop 20200512145953
Bug: https://bugs.gentoo.org/909980 Signed-off-by: Sam James <sam@gentoo.org> - Sam James · gentoo
dev-build/gyp: stabilize 20200512145953-r1 for amd64, ppc64, x86
Bug: https://bugs.gentoo.org/909980 Signed-off-by: Sam James <sam@gentoo.org> - Repository mirror & CI · gentoo
Merge updates from master - Sam James · gentoo
dev-build/gyp: port to python-single-r1
The package isn't suitable for PEP517, as it installs data files and it simply happens to be written in Python, rather than intending to be imported and so on. Unfortunately, for the remaining PEP517 holdouts, there's little pressure upstream for them to port to a proper build system yet, as while setuptools deprecated the `setup.py` entrypoint some time ago, there's no removal in sight yet, so the only pressing side is on Gentoo's where we want to cleanup distutils-r1's support for that. It was arguably a mistake to really have these packages use distutils-r1 in the first place. The obvious workaround for now is to invoke setup.py manually w/ python-single-r1, and punt the question until setuptools removal of the entrypoint looks closer (at which time, other distros will be putting pressure on upstreams too). Of course, if at the time of such a setuptools change, the package is still not fixed, then we'd have to remove it. (The same issues apply to bug #922396 which isn't fixed by this, but hopefully won't be an actual problem until that aforementioned removal in setuptools itself of the other bits.) Bug: https://bugs.gentoo.org/922396 Closes: https://bugs.gentoo.org/909980 Closes: https://bugs.gentoo.org/923435 Closes: https://bugs.gentoo.org/952274 Signed-off-by: Sam James <sam@gentoo.org> - Repository mirror & CI · gentoo
Merge updates from master - Sam James · gentoo
dev-build/gyp: enable py3.12
With reluctance given the test issues, but users report it works ok for them for mozc, which is all gyp is for. Bug: https://bugs.gentoo.org/929323 Closes: https://bugs.gentoo.org/929378 Signed-off-by: Sam James <sam@gentoo.org> - Repository mirror & CI · gentoo
Merge updates from master - Michał Górny · gentoo
Move {dev-util → dev-build}/gyp
Signed-off-by: Michał Górny <mgorny@gentoo.org>