From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E865B158083 for ; Mon, 23 Sep 2024 21:20:19 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B2865E2A51; Mon, 23 Sep 2024 21:20:14 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2F651E2A3C for ; Mon, 23 Sep 2024 21:20:13 +0000 (UTC) Received: from host81-136-75-24.range81-136.btcentralplus.com ([81.136.75.24] helo=[192.168.1.65]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1ssqTc-000000002e0-3Qs0 for gentoo-user@lists.gentoo.org; Mon, 23 Sep 2024 22:20:12 +0100 Message-ID: Date: Mon, 23 Sep 2024 22:20:16 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [gentoo-user] Wayland! Beware of! To: gentoo-user@lists.gentoo.org References: Content-Language: en-GB From: Wol In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 1cb4d362-aaee-4f19-bac9-7ba563f004da X-Archives-Hash: 20fa173075a0906d53426384974a9ae2 On 23/09/2024 21:14, Alan Mackenzie wrote: > What on Earth is going on? I never asked for wayland, and I haven't > received any news items about it in the last few weeks. I know little > about this X substitute, but one thing's vitually certain; that > installing it as emerge intended would lead to a lot of breakage. Well, everything is slowly moving to Wayland, or X13 as they didn't call it. And while I don't understand the details, X Org is basically dead. X comes in two halves, the front end (or server, they use the words the other way round to normal), which is still maintained. And the back end, or client, that drives the hardware - this bit is basically abandonware apart from the Wayland compositor or whatever it is. So put pretty simply, Wayland is fast becoming - if it isn't already - a hard dependency of X11. But if you want to run X11 as your sole windowing system, that's no problem, just run it over Wayland. What makes you think that enabling Wayland will cause breakage? It shouldn't really do anything much, other than allowing apps to access Wayland features if they want. Given that both KDE/Plasma, and Gnome, are moving to Wayland (and pretty much hide Wayland from you, just like they hide X), I would have thought disabling Wayland was actually MORE likely to cause breakage. Not that your hardware/X combo is going to bitrot, but the apps you rely on might start relying on Wayland and won't be happy if they can't find it. (I'm cursing Plasma 6, but that's not Wayland's fault. afaict it's having problems importing/updating the old Plasma 5 settings with the result it resets itself every time I log in :-( Cheers, Wol