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 9146F158041 for ; Sun, 7 Apr 2024 12:31:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 62450E2A38; Sun, 7 Apr 2024 12:31:42 +0000 (UTC) Received: from smtp7.ctinetworks.com (smtp7.ctinetworks.com [205.166.61.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1C1FCE2A2E for ; Sun, 7 Apr 2024 12:31:41 +0000 (UTC) Date: Sun, 07 Apr 2024 18:01:52 +0530 (IST) Message-Id: <20240407.180152.1533542310117167076.enometh@meer.net> To: gentoo-dev@lists.gentoo.org, Florian Schmaus Subject: [gentoo-dev] Re: Update on the 23.0 profiles In-Reply-To: (Florian Schmaus's message of "Sun, 7 Apr 2024 13:35:45 +0200") From: Madhu References: <10606960.T7Z3S40VBb@noumea> X-Mailer: Mew version 6.9 on Emacs 30.0.50 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ctinetworks-Information: Please contact the ISP for more information X-ctinetworks-MailScanner-ID: 67DB812BB07.A5502 X-ctinetworks-VirusCheck: Found to be clean X-ctinetworks-SpamCheck: X-ctinetworks-Watermark: 1713357101.01153@nC/lMQ9YVEOTNJzli9lQYA X-Archives-Salt: 4d0ae963-cee1-4ab9-92b0-c16c5ca32be4 X-Archives-Hash: d3fe305851f2488642b0c2e6dac5de02 > Thanks for the update and the work on the 23.0 profiles. :) >> Most 17.x profiles have been downgraded to "exp". > I could imagine there is a reason to downgrade those back to 'exp', > could you elaborate a bit on that? > > Isn't it bit strange that a 'stable' profiles gets downgraded back to > 'exp'? Then again, I am not sure about the implications of this nor > about the rationale behind it. > > However, I also notice that there is a outstanding PR that reverts > that [1]. Maybe we should introduce a new state 'oldstable' or so? I see no way of migrating to 23.0 profile because of not-recompilable packages that are installed (over 4 years) which block --emptytree, and do not wish to be forced to migrate to merged-usr on an openrc box without a compelling need (on principle). Will patching back the 17.0 profile files into the portage tree if and when they are removed work? Are there any options at all for this situation (like freezing the the last supported tree protecting it from emerge-syncs, and using an overlay for further updates?)