Re: xserver policy

Hey,

As for the Wayland policy module, I've been looking into various compositor=
s on
other desktops to see how they function and what they need. xdg-desktop-por=
tal
specifically has given me a bit of grief whilst designing, and many of the =
big
desktop environments make use of it.

As for xdm_t specifically, I have been looking into that myself. Russell ma=
kes
a good point about the xserver module being required for a lot of things th=
at
are not really related (e.g. fonts and mesa labelling iirc).

I've been playing around with greetd at present as it's small enough that i=
t
should be a good login manager (that's the "new" term) to design with. It i=
s
also noteworthy that plasma has a new login manager in the works too which =
is
a fork of sddm, so that might provide some opportunity for design there too=
.

However, I would personally be opposed against dropping xserver entirely, a=
t
least for now. There are still a couple desktops using it, and I think this=
 is
something that should be taken with caution. However, dropping XACE support=
 if
it adds significant complexity seems reasonable to me right now.

The other thing to consider is Xwayland. I don't personally use it (or Xorg=
) at
all myself, however I do know that some stuff still requires Xwayland and i=
t is
very common as of 2026. It might be worth seeing if there is some bits that=
 we
can share between a future xwayland_t and xserver_t, although that may turn=
 out
to be a fruitless endeavour, I'm not entirely sure what Xwayland entails ye=
t.

--=20
Rahul Sandhu