I realize now that this patch will only fix local (ie $PREFIX) installs
of xwayland, and that something else needs to be done so that real
system installs of wayland will work.
The problem is if an /etc/X11/xorg.conf file exists, Xorg --wayland
attempts to read it. If the text in the file causes the wayland backend
to not work then it exits. This file may very well exist because the
same machine is being used to run a legacy X server as well as wayland.
I now think the best solution is to make Xorg --wayland use a different
configuration file, perhaps /etc/X11/wayland.conf. This is especially
true because I believe a non-existent config file will often work and
this is the easiest way to indicate that when an xorg.conf file exists.
Would love to have some feedback:
1. Is this really a bug or am I missing something obvious?
2. Is the idea of a different conf file the right one? Is my proposed
name the right one?
3. If so is the best way to have weston add a --config switch when
running Xorg, or modify the source code for Xorg?
4. Is rearranging the search path (ie this patch) in Xorg to look in
$PREFIX first a good idea anyway? I and others on this list certainly
expected it to work this way and it took some time before I figured out
it was literally doing things differently than any other Linux software.
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
