On 2025-11-30 at 14:36, Mike McClain wrote: > I guess I'm confused, thinking wayland sits on top of X11 rather than > X11 depends on wayland. > Thinking I'm using X11 rather than wayland I went to purge wayland. > root@RPI2:~> apt purge libwayland* > REMOVING: firefox galculator x11-utils xserver-xorg* > I declined this. > Can someone explain why purging libwayland* would necessitate removing > xserver-xorg*? On my system, the chain appears to be: xserver-xorg-core -> libegl1 -> libegl-mesa0 -> libwayland-client0 I'd guess (but this *is* only a guess) that there's a "use Wayland if it's available" setup going on in libegl-mesa0, and it does the check for whether Wayland is available by calling functions from libwayland-client0, similarly to how so many things call functions in libsystemd0 to find out whether systemd is available. What the reasoning is I couldn't say beyond that (I'd have to do some digging), but it's likely the same basic chain will apply. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature