04-27-2025, 11:31 AM
(04-25-2025, 08:21 PM)Kevin Kofler Wrote: Probably never. Someone needs to package it in a third-party repository.
The way to package this is:
1. clone https://github.com/kkofler/gtk
2. generate the patch: git diff 4.18.4..gtk-4-18-4-gl2 >gtk-4.18.4-gles2.patch
3. remove the 2 hunks that delete binary PNGs from the patch – the release tarball apparently has some PNG optimizer run on them, so they do not match the version in git and applying the patch fails
4. get the packaging sources for GTK 4 (version 4.18.4 if possible) for your distribution
5. add the patch to the package and make sure it gets applied (this varies from distribution to distribution)
6. after applying the patch, add another line to the build-time package scriptlets to manually delete the PNGs whose deletion was removed from the patch in 3: rm -f testsuite/gsk/compare/huge-height-hdr.png testsuite/gsk/compare/huge-width-hdr.png (though I think you will get away without doing that, the PNGs will just not be used)
7. build the modified package and upload it to a repository
I have done that for Fedora here: https://copr.fedorainfracloud.org/coprs/....18-gles2/
For Debian, see https://wiki.debian.org/Packaging for the distribution-specific packaging instructions (steps 4 to 7).
Maybe there's something I don't understand. Could Megapixels use the GSK renderer based on Vulkan to solve this problem?