public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Arthur Zamarin <arthurzam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Notion of stable depgraph vs stable keywords (Re: [gentoo-dev] Arch Status and Future Plans)
Date: Wed, 26 Jun 2024 01:06:12 +0100	[thread overview]
Message-ID: <87h6dgpnyj.fsf@gentoo.org> (raw)
In-Reply-To: <75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org> (Arthur Zamarin's message of "Tue, 25 Jun 2024 20:33:05 +0300")

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

Arthur Zamarin <arthurzam@gentoo.org> writes:

> Hi all, this will be a long mail, and might be confusing, I'll try to
> organize it, but this is a mess, so bear with me.

Absolutely - thanks for doing this. I'm going to split my replies with
alt subject to help keep it organised.

>
> 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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  parent reply	other threads:[~2024-06-26  0:06 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 ` Sam James [this message]
2024-06-28  4:17   ` [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: Arch Status and Future Plans) Duncan
2024-06-28  5:16     ` 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=87h6dgpnyj.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --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