David Heidelberg
David Heidelberg
Hello @Slaw6820 thank you for the contribution, could you split the one commit into the separate changes?
> Sure. Does it mean that all proposed fixes are accepted? Should I create multiple changes under one PR or separate PRs? LTGM, but I'm not an biggest authority here...
The idea looks good to me, could you do "full package"? https://udd.debian.org/patches.cgi?src=apitrace&version=11.1%2Brepack-1.2 For example if I drop snappy from submodules, it won't allow me replace it with system package as...
[trace.tar.gz](https://github.com/apitrace/apitrace/files/12403398/trace.tar.gz)
I would wait a bit with merging something like this, since other possible solutions are proposed in https://bugreports.qt.io/browse/QTBUG-115731 . In worst case it would be nice if it would be...
I would prefer the workaround to be applied only where necessary, such as detecting or defining broken configurations. If it's not easily possible, then I suppose I would be okay...
@Mis012 it's not usually visible, but since more than year passed, option to disable GLX at ~build~run-time could be appropriate since it's getting into background.
Something like: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28576 ? Would be nice to have in meson, thou not sure for how many project it's really useful. I understand that Firefox and LibreOffice make sense, but...
for lm-sensors, there has been this issue: https://github.com/groeck/lm-sensors/issues/5
Bump, the issue is still valid. Please revert if possible!