A new version of intel-gpu-tools 1.15 has been available for a while - let's make it available! https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/commit/?id=3ce58b6f9502329d03207a786301d077e7f0cf6c Reproducible: Always Steps to Reproduce: 1. emerge intel-gpu-tools 2. intel-gpu-tools is version 1.12 Expected Results: intel-gpu-tools is version 1.15
Created attachment 437096 [details] ebuild for 1.15 rev bump
*** Bug 580718 has been marked as a duplicate of this bug. ***
in the future, please post diffs rather than entire ebuilds pretty sure that removal of python code is incomplete. since the only thing using it was the dumper script, we can drop python entirely. done so here: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0b4988cbbc38a1c5f99c829b638f248255382935
Shader debugger in intel-gpu-tools still needs python. Hence had kept python in the ebuild.
(In reply to Azhar from comment #4) what shader debugger ? none of the installed files are python scripts or are linked against libpython that i can see.
(In reply to SpanKY from comment #5) > (In reply to Azhar from comment #4) > > what shader debugger ? none of the installed files are python scripts or > are linked against libpython that i can see. shader debugger -- is an optional feature, which on enabling acts like a debug server accepting connections from debug clients such as mesa.
(In reply to Azhar from comment #6) but it's not enabled+installed by the ebuild right ? random scripts that might be in the tarball but not actually installed are not tracked by the ebuild.
It might be automagic. # Define a configure option for the shader debugger AC_ARG_ENABLE(shader-debugger, AS_HELP_STRING([--enable-shader-debugger], [Enable shader debugging support [autodetected]]), [BUILD_SHADER_DEBUGGER="$enableval"], [BUILD_SHADER_DEBUGGER=no])
(In reply to Chí-Thanh Christopher Nguyễn from comment #8) that help string is wrong ;). the default behavior is to disable, not autodetect. looking the code that enables though, python still doesn't matter: - nothing includes/links python - the single python script (pre_cpp.py) is not installed - pre_cpp.py is run to generate some source files (which would mean we want python-any-r1 if we were to build this code), however ... - all the output of pre_cpp.py is noinst_*, so we'd disable them anyways to avoid wasting time on things not built+installed - the only program under that tree that is actually installed "eudb", and that's a standalone C program so i'm still not seeing why we'd need or care about python in the ebuild
