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 103D115802E for ; Fri, 28 Jun 2024 04:17:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EA81AE2A43; Fri, 28 Jun 2024 04:17:53 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 17DFCE2A3C for ; Fri, 28 Jun 2024 04:17:53 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1sN33X-0002hN-Ac for gentoo-dev@lists.gentoo.org; Fri, 28 Jun 2024 06:17:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: Arch Status and Future Plans) Date: Fri, 28 Jun 2024 04:17:46 -0000 (UTC) Message-ID: References: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> <87h6dgpnyj.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; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: Pan/0.159 (Vovchansk; 873418b69f5cd62f5acb4f8908b7bbeeeccdb546) X-Archives-Salt: 6fcb6226-922a-4fd5-94fa-64b70f699e4f X-Archives-Hash: 5c2da10e849dda712565e9306009474e 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, it's still confusing from a user perspective (even a long-time user like me who religiously follows this list, tho being on amd64 personally with no question on it staying stable it doesn't really affect me personally at this time... tho not /too/ long ago I was still running a 32-bit-only atom netbook (tho only upgraded perhaps every year or two... which always made it difficult but possible with some time and patience) so it /could/ still affect me and I'm concerned about others still affected). Taking the one most likely to affect the greatest number of users as an example, what practical effects would dropping x86 to dev (I'm assuming no one's suggesting dropping it straight to experimental) have on remaining x86 users? 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? -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman