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 D548D158083 for ; Mon, 23 Sep 2024 21:12:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7E7D0E2A5C; Mon, 23 Sep 2024 21:12:25 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (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 0BE52E2A34 for ; Mon, 23 Sep 2024 21:12:25 +0000 (UTC) From: =?utf-8?Q?Arsen_Arsenovi=C4=87?= To: Alan Mackenzie Cc: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Wayland! Beware of! In-Reply-To: (Alan Mackenzie's message of "Mon, 23 Sep 2024 20:14:26 +0000") Organization: Gentoo References: Date: Mon, 23 Sep 2024 23:12:17 +0200 Message-ID: <86frpq3wi6.fsf@gentoo.org> 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 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: 9bcac9a9-1260-43cd-a84f-9ca77097bf8c X-Archives-Hash: a74917a045a5ca9e1b4ebb44519aec9a --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello, Alan, Alan Mackenzie writes: > Hello, Gentoo. > > I got a nasty shock earlier on this evening when I was updating my > (still newish) system. Around (perhaps) 70 packages to be updated or > reloaded, several of them big packages. What's going on? > > There were lots of qt and kde packages being sucked in. But what stood > out prominently was the wayland USE flag, which appeared to have been > enabled in most of these packages. > > 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. That should not be the case. If something breaks, that's a bug. Wayland was added to the default USE of the desktop profiles because most DE developers have started phasing out X11 support, or at least treating it as second-class, and because enabling USE=3Dwayland should have no impact on those using the X session, as most/all Wayland support is runtime-conditional. So, that change agrees with developers of software we ship, while not bringing our users much disadvantage. Hence it was enabled. Hope that helps, have a lovely evening. =2D-=20 Arsen Arsenovi=C4=87 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOcEARYKAI8WIQT+4rPRE/wAoxYtYGFSwpQwHqLEkwUCZvHZsV8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0RkVF MkIzRDExM0ZDMDBBMzE2MkQ2MDYxNTJDMjk0MzAxRUEyQzQ5MxEcYXJzZW5AZ2Vu dG9vLm9yZwAKCRBSwpQwHqLEk80BAP9DOuzbqdR9C/YO9uVrxenmBSZoWtq7YC5a 13r7D57zEAEA82ivEteJDv70p4YyELscSdMuvUlbaT1U5FWOdVOEhg8= =kxNl -----END PGP SIGNATURE----- --=-=-=--