public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
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)	[thread overview]
Message-ID: <pan$3d027$edf24b57$229a0fe7$bf170003@cox.net> (raw)
In-Reply-To: 87h6dgpnyj.fsf@gentoo.org

Sam James posted on Wed, 26 Jun 2024 01:06:12 +0100 as excerpted:

> Arthur Zamarin <arthurzam@gentoo.org> 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



  reply	other threads:[~2024-06-28  4:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 17:33 [gentoo-dev] Arch Status and Future Plans Arthur Zamarin
2024-06-25 21:40 ` matoro
2024-06-25 22:55 ` James Le Cuirot
2024-06-26  0:06 ` Notion of stable depgraph vs stable keywords (Re: [gentoo-dev] Arch Status and Future Plans) Sam James
2024-06-28  4:17   ` Duncan [this message]
2024-06-28  5:16     ` [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: " Sam James
2024-06-26  0:14 ` Misc arch plans (Re: [gentoo-dev] " Sam James
2024-06-26 20:29   ` ia64, was: " Andreas K. Huettel
2024-06-26 20:45     ` matoro
2024-06-26  0:17 ` On the value (or not?) of stable keywords " Sam James
2024-06-26  0:19 ` time64 & LFS for 32-bit arches " Sam James
2024-06-26  0:20 ` x86 FP issues " Sam James
2024-06-28  5:20   ` Michał Górny
2024-06-26  7:38 ` [gentoo-dev] Re: Arch Status and Future Plans Florian Schmaus
2024-06-26  8:29   ` Christian Bricart
2024-06-26 20:44   ` Immolo
2024-06-26 19:47 ` nomenclature, was: Re: [gentoo-dev] " Andreas K. Huettel
2024-06-26 20:18 ` Andreas K. Huettel
2024-06-26 20:24 ` riscv, was: " Andreas K. Huettel
2024-06-26 21:08 ` 32bit vs 64bit, " Andreas K. Huettel
2024-06-28 16:12 ` splitting keywords, " Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$3d027$edf24b57$229a0fe7$bf170003@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox