Pekka Paalanen wrote:
On Mon, 03 Sep 2012 13:36:47 -0700
Bill Spitzak <[email protected]> wrote:
I think changing the name at the lowest level as I did it is the correct
solution. I see no way anybody can use this unless they can tell the x
server to ignore any existing xorg.conf file. Changing it at the final
program seems much cleaner than requiring every wrapping program to pass
a --config switch.
Btw. did you ever test that your config name changes work also with
config dirs, like /etc/X11/xorg.conf.d/?
Don't take this as on opinion about what is the right approach, only
X.org server devs can take a stand (i.e. the discussion should be cc'd
to the appropriate mailing list). This is just a detail that came to my
mind.
I did not do any real testing, but it looked like all uses of those %C
and %P, etc, symbols was that all the search paths looked in / first and
then in $PREFIX second. This meant that it was impossible to override a
system file by putting something into $PREFIX.
However I then realized that changing the search path would not fix any
xwayland because a "real" installation would not have a $PREFIX anyway,
so there had to be a different method to give wayland a different .conf
file. So at that point I switched to using a different name for the
.conf file.
I don't know if there are other conflicting files in xorg.conf.d. If so
they may need renaming for the wayland version too.
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
