Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: mesa update looks suspicious (Read 881 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

mesa update looks suspicious

This does not seem right:
Code: [Select]
Package (8)          Old Version  New Version  Net Change  Download Size
...
world/mesa           1:25.0.5-1   1:25.1.1-1   -60.39 MiB      10.15 MiB
I seem to recall similar cases with mesa in the past, and then the package was crippled by accident. (OTOH, if they actually shaved 60 unnecessary MiB off of mesa, that's great!)

Re: mesa update looks suspicious

Reply #1 –
In case anyone is curious, the reason is apparently an upstream change in what's supported: https://www.phoronix.com/news/Mesa-Stop-Building-XA

I even compared the lists of installed files; the new versions is missing the libs 'd3dadapter', 'libxatracker', 'libOSMesa', of which at least the first two are explained by the above piece of news (the third has to do with headless rendering?). These libs used to add up to about 62M, so actually the rest of mesa got a bit fatter...

For the record, I know nothing of the internals of mesa. Just toying around with pacman.
 

Re: mesa update looks suspicious

Reply #2 –
Fuck, now that's a real stab to X users
ARMtix
If you need to contact me, use email

Re: mesa update looks suspicious

Reply #3 –
Quote from: phoenix_king_rus – on
Fuck, now that's a real stab to X users
Quote from: itsZariep – on
Mesa deprecated Gallium Nine (/usr/lib/d3d/d3dadapter9.so.1) in version 25.2, and it is therefore no longer included in the package. As a result, this package is now unusable. It might be time to either remove it or find a workaround?
This article says that building "Gallium-XA" is disabled by default. So it still can be built.

I suggest that the PKGBUILD either builds it, or that a separate package is created which installs this (and adjust dependencies accordingly).

But this only would help for now, since the code might likely totally be dropped out of Mesa in version 25.2 according to the linked article.

Regards!