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 A3BF7158083 for ; Mon, 23 Sep 2024 20:14:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D6C19E2A4D; Mon, 23 Sep 2024 20:14:31 +0000 (UTC) Received: from mail.muc.de (mail.muc.de [193.149.48.3]) (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 3A084E2A44 for ; Mon, 23 Sep 2024 20:14:30 +0000 (UTC) Received: (qmail 11987 invoked by uid 3782); 23 Sep 2024 22:14:26 +0200 Received: from muc.de (p4fe15589.dip0.t-ipconnect.de [79.225.85.137]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Mon, 23 Sep 2024 22:14:26 +0200 Received: (qmail 6210 invoked by uid 1000); 23 Sep 2024 20:14:26 -0000 Date: Mon, 23 Sep 2024 20:14:26 +0000 To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Wayland! Beware of! Message-ID: 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: text/plain; charset=us-ascii Content-Disposition: inline X-Submission-Agent: TMDA/1.3.x (Ph3nix) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: 9c20a8d2-4f8a-47d3-ba92-136e1a92d8b5 X-Archives-Hash: 87f16565336f263637c545ff5d001a0f 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. So I disabled the wayland USE flag in my make.conf, and the number of packages to merge went down to 29. I merged them. I'm hoping my machine is still stable. It would have been nice to have got a news item about this change. :-( -- Alan Mackenzie (Nuremberg, Germany).