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 3758C15802E for ; Fri, 28 Jun 2024 05:16:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5B19D2BC01E; Fri, 28 Jun 2024 05:16:47 +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 0D6C82BC016 for ; Fri, 28 Jun 2024 05:16:47 +0000 (UTC) From: Sam James To: Duncan <1i5t5.duncan@cox.net> Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: Arch Status and Future Plans) In-Reply-To: (Duncan's message of "Fri, 28 Jun 2024 04:17:46 -0000 (UTC)") Organization: Gentoo References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> <87h6dgpnyj.fsf@gentoo.org> Date: Fri, 28 Jun 2024 06:16:42 +0100 Message-ID: <87bk3l3av9.fsf@gentoo.org> 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 X-Archives-Salt: bae6b35f-7bb7-4dd9-b07f-9798e92272af X-Archives-Hash: 67b029eb9e70c1e9744a1220debde55d Duncan <1i5t5.duncan@cox.net> writes: > Sam James posted on Wed, 26 Jun 2024 01:06:12 +0100 as excerpted: > >> Arthur Zamarin writes: >> >>> As you all know, Gentoo supports many various arches, in various >>> degrees (stable, dev, exp). Let me explain those 3 statuses fast: >>> >>> * stable arch - meaning we have stable profile for this arch, and >>> stable keywords across base-system + varying degree of seriousness. We >>> stable stuff after ~30 days in tree, and are mostly happy. For example >>> the well known and common amd64 arch. >> >> This mixes the notion of keywords vs profiles. >> >> You can have a stable profile in profiles.desc without any stable >> keywords at all. >> >> 'stable' in profiles.desc means we require CI to pass for its depgraph >> consistency. 'dev' means we warn on it. 'exp' means it doesn't even show >> up unless you opt-in with pkgcheck etc. > > While that may clear things up from a developer perspective, The discussion we're currently having *is* from a developer perspective where I'm trying to clarify something Arthur said for the purposes of further discussion. > > How would it differ if they're already running ~x86 vs stable x86 > (keywording), assuming the same currently stable x86 profile? > > And (again from a user perspective) how does dropping x86 to dev differ > from the mentioned apparently worse alternative, mass dekeywording? An inconsistent depgraph is a very poor experience for users because there's no guarantee emerge can resolve things.