Created attachment 215906 [details]
I'd like to make sure nothing accidentally uses X11.
OPTIONS_UNSET += X11
graphics_cairo_UNSET += XCB
x11-toolkits_gtk30_UNSET += ATK_BRIDGE COLORD
(In reply to Jan Beich from comment #0)
Apologies in advance; as I have no doubt that
what you're doing here _should_ be done. But
I can't help but ask;
doesn't the X in libxkbcommon _imply_ X11?
Or was it poorly named?
(In reply to Chris Hutchinson from comment #1)
See pkg-descr and https://wayland-book.com/seat/xkb.html. As Wayland often needs to support Xwayland (X11 apps on Wayland) and X11 session (Wayland apps on X11) it's easier if keymaps are handled by one API.
(In reply to Jan Beich from comment #2)
Thank you very much, Jan. I guess I should have already
Thank you for taking the time! :-)
I don't think we need to merge it to Q3.
A commit references this bug:
Date: Sat Jul 11 17:45:18 UTC 2020
New revision: 541999
x11/libxkbcommon: make X11 optional
Approved by: zeising