Any ideas on what to do about xorg.conf?
I think the ideal solution is to make the "special X.org server" just
not read any configuration files at all. My impression is that the need
to use one to load wlshm on my system is an easily-fixed bug. And it
would seem that any need for "configuration" would indicate a failure of
Wayland's api to provide necessary information.
Unless something is done to make it ignore existing xorg.conf and
xorg.conf.d files, it will be impossible to run Wayland on a machine
where the user may also want to run old-style X11. Although in the end
this is probably unimportant when everybody runs wayland, I think it is
a show-stopper bug for any initial adoption of wayland.
Pekka Paalanen wrote:
The generic module loading must be used now to load xserver.so.
Option --xserver was removed by
a6813d28876423b388cce3ff6d7edab7b9de0f20.
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
