|
|
|
|
|
|
by majewsky
3135 days ago
|
|
|
I think there's some misunderstanding in your comment about how Wayland works. 99.9% of Wayland desktops out there [1] do not use Weston. Weston is not Wayland's display server, it's a reference implementation of a window manager implementing the Wayland protocol(s). There is no separation between display server and window manager in Wayland, only a single master process, the compositor, which fulfils (roughly) both these roles. So if you're running, say, KDE Plasma, then your compositor is KWin, and Weston is nowhere to be seen. If you're running Sway, then your compositor is Sway. And so on. Wayland is only a protocol, not a piece of software (unless you count the shared libraries provided by the Wayland project). [1] Guesstimate. |
|
|