You are not logged in.
Today while updating i have noticed I have wayland installed on my system even though I never explicitly installed it (I use X). Then I tried to remove it because I obviously do not need it, but it seems like it is required by a bunch of packages:
:: removing wayland breaks dependency 'wayland' required by gst-plugins-bad-libs
:: removing wayland breaks dependency 'wayland' required by gst-plugins-base-libs
:: removing wayland breaks dependency 'wayland' required by gtk3
:: removing wayland breaks dependency 'wayland' required by libva
:: removing wayland breaks dependency 'wayland' required by mesa
:: removing wayland breaks dependency 'wayland' required by mpv
:: removing wayland breaks dependency 'wayland' required by webkit2gtk
:: removing wayland breaks dependency 'wayland' required by wpebackend-fdo
Does anyone know why that is?
Last edited by lordfarquaad (2023-04-10 13:05:13)
Offline
Simply speaking: Because support for Wayland is build into that packages.
Offline
The wayland-package is small and only contains a few libraries that are necessary for applications to be able to talk with a wayland compositor (the compositor is the server part). You can compare it to libx11, but it is much smaller than that package.
Those libraries cannot be removed when you have applications that are compiled with wayland support.
Last edited by progandy (2023-04-10 09:06:37)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
thanks for clearing things up. closing the thread.
Offline