commit: 354e2730b18c97438e35b14c180fec7452314486
parent 5445253c6699e7030a853037a003127f00193eff
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Mon, 9 May 2022 22:45:46 +0200
notes/pure-wayland: Note on global status
Diffstat:
1 file changed, 1 insertion(+), 0 deletions(-)
diff --git a/notes/pure-wayland.shtml b/notes/pure-wayland.shtml
@@ -8,6 +8,7 @@
<!--#include file="/templates/en/nav.shtml" -->
<main>
<h1>non-XOrg Wayland</h1>
+ <p><strong>2022-05 note</strong>: It's getting really rare for something to not work unless it's stuck to X11 or it's badly linking to OpenGL, consider that most things "Just Works", unless I described a problem and it's still there.</p>
<p>
<strong>Warning:</strong> This is Wayland without any of <code>libX11</code> or related (ie. <code>libGL.so</code> instead of <code>libOpenGL.so</code>) in the system, this also removes the <code>XWayland</code> compatibility layer as it's an xorg-server component.<br/>
You can find this kind of similar setup in embedded systems (ie. SailfishOS), as X11 makes no sense outside of keyboard+mouse setups, but I don't expect it until a bunch of years for regular desktops (say when X.Org will have died), I'm doing this right now to avoid having to rush to get rid of X11 with having to push the End-of-Life date way back it's upstream date (that happened with python-2 because it wasn't much prepared until the last year or two).<br/>
