dev-python/glfw
A ctypes-based wrapper for GLFW3
Screenshots
-
glfw-2.10.2~amd64 ~x86python_targets_python3_14t python_targets_python3_15t python_targets_python3_12 python_targets_python3_13 python_targets_python3_14 python_targets_python3_15
View 
Download 
Browse License: MIT Overlay: benzene-overlay -
glfw-2.10.2~amd64 ~arm64python_targets_python3_12 python_targets_python3_13 python_targets_python3_14
View Download Browse License: MIT Overlay: stuff -
glfw-2.10.1~amd64 ~arm64python_targets_python3_12 python_targets_python3_13 python_targets_python3_14
View Download Browse License: MIT Overlay: stuff
ChangeLog
commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit 554e70e175b10b341a35dab7701482cd0484542a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jul 22 15:45:47 2026 +0200
dev-python/glfw: add 2.10.2
commit f437c66fbb4b6078f44fa14640c1dfecc0753420
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Jul 17 15:15:55 2026 +0200
dev-python/glfw: add 2.10.1
commit b8fb09d9c27040c16e14b8c648370498e02db5bb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 16 14:08:41 2026 +0200
dev-python/glfw: Keyword 2.10.0 for ~arm64
Pure-Python (PEP517), architecture-independent.
commit d9bd36781b89a0b33847e65077b83c65c7697b1c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jun 14 20:56:20 2026 +0200
dev-python/glfw: add 2.10.0
Python ctypes bindings for GLFW; ComfyUI's 3D-preview nodes use it, gated under USE=opengl in the comfyui ebuild. Forked from ::guru into ::stuff so the overlay carries no guru master dependency. dlopens media-libs/glfw at runtime.
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit 554e70e175b10b341a35dab7701482cd0484542a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Jul 22 15:45:47 2026 +0200
dev-python/glfw: add 2.10.2
commit f437c66fbb4b6078f44fa14640c1dfecc0753420
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Jul 17 15:15:55 2026 +0200
dev-python/glfw: add 2.10.1
commit b8fb09d9c27040c16e14b8c648370498e02db5bb
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 16 14:08:41 2026 +0200
dev-python/glfw: Keyword 2.10.0 for ~arm64
Pure-Python (PEP517), architecture-independent.
commit d9bd36781b89a0b33847e65077b83c65c7697b1c
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jun 14 20:56:20 2026 +0200
dev-python/glfw: add 2.10.0
Python ctypes bindings for GLFW; ComfyUI's 3D-preview nodes use it, gated under USE=opengl in the comfyui ebuild. Forked from ::guru into ::stuff so the overlay carries no guru master dependency. dlopens media-libs/glfw at runtime.