I was able to get Qtile running just fine in a VM on X11, I can’t reproduce with Wayland.
Forgive my noobness - I daily F40 XFCE, This is quite out of my comfort zone but interesting, I’m trying to understand better.
I think I’m too deep trying to use ninja and meson to build from source…
Somehow I manage to actually get Ninja-Build, Meson, and the respective tools to work, but I’m already stumped because I’m not sure what’s the “PREFIX” where the libraries should be installed (presumably a directory I need to make at /usr/lib/wayland ??)
I already nuked my VM out of frustration, so no logs… I’ll start from scratch again but I would get an error when I tried to run Qtile:
qtile start -b wayland
Along the lines of…
“Wayland Backend Not Built” “libEGL warning: egl: failed to create dri2 screen”
What packages/ dependencies do I need for Wayland back-end to be built for CentOS Stream 9?
I would prefer to just have the required libraries.
I feel like there has to be an easier method considering RHEL defaulting to Wayland protocol right?
I don’t mind walking through installation from source if that’s the only route here outside of a full-blown DE. Any advice?
I believe perhaps you’re unaware… Qtile does offer a Wayland configuration/ can serve as a Wayland compositor now. It’s actually at the bottom of the list that you sent.
Also, you didn’t quite address what my concern/question was about - How do I build/prepare Wayland back-end so that I can “insert” my compositor of choice and it will function correctly…
Thanks for bringing the EPEL repo. to my attention - I was unfamiliar with that.
But I think I want to avoid those for now -
There are a number of wayland related packages available through DNF:
wayland-devel-x.x-x
wayland-protocols-devel-x.xx.x
wayland-utils-x.x.x
egl-wayland-x.x.x
but I couldn’t get them to function properly with the Qtile…
I’ll try to take another crack at building from source, I’m looking over the documentation again and reading through all the steps before getting started. Hopefully I can reference in between similar projects to put this together.
Also, I don’t feel like it’s a matter of the packages not being up-to-date. Unless I’m mistaken RHEL 9 defaults to Wayland Gnome - and if CentOS Stream 9 is upstream wouldn’t that mean that our packages should be newer?
I notice it’s referring to xkbcommon, I downloaded the available packages related to xkbcommon, and cffi, furthermore I built from source using pip…
Again, I appreciate the assistance and feedback! Is this the dependency hell that people are talking about with Wayland?
Then again - Maybe I’m just too novice, but I thought it might be simpler to implement, especially since it’s supposed to be an improvement to the complexity of X11.
I think it is dependency hell in general. Package managers take care of it all for you, but if the software is not packaged for your platform, then you are on your own and have to deal with it yourself.
I’ll start from scratch again 
but I would get an error when I tried to run Qtile:
