kitty: Add version 0.48.2 but DO NOT INSTALL #3452
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Self-contained build: FreeType 2.14.3 (needed for the FT_Get_Color_Glyph_Paint/COLRv1 API kitty's freetype.c uses unconditionally) is built privately as a static/PIC library under ${B} and linked directly into fast_data_types.so, rather than bumping the shared freetype.be0 used by cairo/fontconfig/etc. simde headers are likewise fetched to ${B} and used only via --extra-include-dirs. Neither touches any other package.
kitty ships its GPU shaders as plain .glsl for OpenGL to compile at runtime in this release, so no Slang/slangc dependency is needed.
DO NOT INSTALL:
this builds cleanly, but kitty/kitten embed a Python interpreter and fast_data_types.so is CPython extension module, so both link directly against libpython3.*.so -- unlike every other python3 consumer in this repo, which goes through python3-wrapper.be0's prun-wrapped shell scripts specifically to avoid
that binary linkage. There's no stable runtime dependency here to link against:
/pkg/python-3.14.6-2 is the live interpreter, but that path is pinned to one package version; an rpath baked into kitty/kitten now goes stale (loading-shared-libraries failure at launch) the moment python gets bumped to python-3.14.7 or whatever comes next.
/usr/local/system/python3 is a stable alias, but it points at a 2019 Python 3.7.2 install, well below kitty's own requires-python >= 3.12 -- not usable at any linkage.
Fixing this for real needs a proper python.be0-style package kitty can declare an actual runtime dependency on, one bee's own install/update tooling tracks, rather than a path guessed at build time. Until that exists, this package should be treated as build-verified only.