uwumeowmeownyaa has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.4)]
lavaball has quit [Remote host closed the connection]
<jaeger>
Guessing you have wayland being pulled in as a dependency to some other package, mesa-32 doesn't explicitly depend on any wayland
<jaeger>
It does check if wayland-protocols is already installed and enable support if so, but not explicitly require it
Tedesfo has joined #crux
Tedesfo has quit [Quit: Leaving]
ppetrov^ has joined #crux
lavaball has joined #crux
ppetrov^ has quit [Quit: Leaving]
ppetrov^ has joined #crux
zorz_ has joined #crux
uwumeowmeownyaa has joined #crux
zorz_ has quit [Quit: leaving]
<cruxbot>
[opt/3.7]: [notify] cups: updated to version 2.4.11
<cruxbot>
[contrib/3.7]: shaderc: updated to version 2024.3
<cruxbot>
[contrib/3.7]: libplacebo: updated to version 7.349.0
<cruxbot>
[contrib/3.7]: mpv: updated to version 0.39
SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux
_moth_ has quit [Ping timeout: 252 seconds]
farkuhar has quit [Quit: nyaa~]
yeloxp has joined #crux
<yeloxp>
hi all just wanted to ask what package would give me wayland-client which mesa-32 needs
<yeloxp>
i already have relevant wayland packages installed btw
<yeloxp>
i can see that on debian there is a libwayland-dev package which provides this
<jaeger>
yeloxp: I think you had left already before I mentioned it but there's no explicit wayland dependency in mesa-32 so it's probably being pulled in by something else you have installed
<jaeger>
Not necessarily a bad thing, just clarifying
<jaeger>
As for the wayland-client it wants, that's probably wayland-32
<yeloxp>
uh yeah i had to leave then
<yeloxp>
yeah installed wayland-32 and its fine now
<yeloxp>
i think wayland is pulled in by steam
<jaeger>
I believe so, yeah
<yeloxp>
i wonder why the client depends on it now
<yeloxp>
when for so many years it didnt
<jaeger>
If you take a look at the Pkgfile (/usr/ports/compat-32/mesa-32/Pkgfile) it checks for 'wayland-protocols' and if it finds that installed it adds wayland support to the configure command
<jaeger>
Oh, maybe you were commenting about the steam client, heh, sorry
<yeloxp>
well i never installed that (wayland-protocols) so idk where that came from
<jaeger>
That's odd, but you could add --all and see non-installed things that depend on it
<jaeger>
I do see it in the steam dependencies list, for reference
<yeloxp>
i dont have any shown package installed
<yeloxp>
i will just uninstall everything wayland-related after steam installs then
<yeloxp>
as i want to keep my system clean yk
<jaeger>
That may break some things but you can always try it for science :)
<yeloxp>
well i know steam and mesa dont need wayland to be installed
<yeloxp>
so maybe everything will be fine
<jaeger>
But if you compile mesa linked with wayland, then uninstall wayland, mesa will be broken
<yeloxp>
ill just recompile mesa then
<yeloxp>
without wayland
<yeloxp>
i got a lot of error about zink and iris modules not built but other that that steam and games do work fine
<cruxbridge>
<tim> libadwaita will pull in wayland for you, and I just checked and it actually builds without it. I guess I can remove that dependency, maybe it got in there by error
<yeloxp>
that explains everything
<cruxbridge>
<tim> I guess the mesa-32 Pkgfile can additionally check if you have wayland-32 installed to make that better too
yeloxp has quit [Quit: leaving]
<cruxbot>
[compat-32/3.7]: mesa-32: check for wayland-32 rather than wayland-protocols