Hi Giovanni, Giovanni Biscuolo <g...@xelera.eu> writes:
[...] >>> ...or apply a patch to rename "~/.cache/mesa_shader_cache" to >>> "~/.cache/mesa<version>_shader_cache" >> >> That's another good idea. > > I was just doing guesswork but the bug caused by this mesa upgrade > smells like a binary incompatibility between two versions (or just major > versions)... so a versioned shader cache makes sense to me > > I'm not able to propose (I mean to code) such a patch, anyway > > Anyway, users should know that they have to periodically clean unused > shader caches, since from what I read on the net the shader cache tends > to really /explode/ in terms of size, in some cases > >>> Alternatively, we should find a way to make Guix users aware of this >>> kind of problems and possible workarounds they can apply (it's not >>> related to this specific bug) >> >> I would rather pursue the other above options you suggest, so that it >> doesn't happen in the first place! I've ping'd upstream with https://gitlab.freedesktop.org/mesa/mesa/-/issues/8937#note_1975560. Let's see what they say! -- Thanks, Maxim
