public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-project@lists.gentoo.org
Cc: Arthur Zamarin <arthurzam@gentoo.org>
Subject: Re: [gentoo-dev] [Proposal] Split arch keywords for ppc64 & riscv
Date: Sun, 04 Aug 2024 20:30:57 +0200	[thread overview]
Message-ID: <10508417.nUPlyArG6x@pinacolada> (raw)
In-Reply-To: <fc1820e9-918a-48ec-a536-56b621d7e240@gentoo.org>

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

Hi Arthur, 

> a. Splitting ppc64 keyword into ppc64 and ppc64le

> b. Splitting riscv keyword into riscv(64?) and riscv32

So in principle these steps both make sense.

The problem is mostly that such an operation on the living Gentoo
has not been attempted in recorded history. There is no precedent in
terms of steps or procedure. Also, it's work.

Which means, we really need to think out the details first and test.

In the following I'm brainstorming a bit, but please see this only as
a very first write-down of incoherent firing of neurons...
In particular, I've not put any thought into whether the tree state is
always formally correct (PMS / CI / ...)

Step 1: Formally introduce the new keywords as "arches".

Step 2: Formally introduce the new keywords in ebuilds by duplication.
Any "ppc64" in keywords becomes "ppc64 ppc64le".
Any "riscv" becomes "riscv riscv32 riscv64".
No exceptions. Can be done automatically. Until the "lock" is removed,
any keywording operations always have to add and remove all of one set.

Step 3: Make new profiles for the new keywords. This is mostly copy-paste, 
I can take care of it.

Step 4: Prepare and publish a migration guide for users.
Right now I assume this will mostly mean "select new profile". However,
I have no clue how portage reacts when $ARCH changes.

Step 5: Deprecate the old profiles, and give people a deadline for migration.
I.e. the LE profiles under ppc64, and all profiles under riscv

Step 6: Remove the old profiles.

Step 7: Lift the "lock" in ebuilds, meaning e.g. ppc64 and ppc64le can be
added and removed independently.

Step 8: Remove all riscv keywords (no 64 or 32)

Step 9: Remove riscv as arch.



-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2024-08-04 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 19:05 [gentoo-dev] [Proposal] Split arch keywords for ppc64 & riscv Arthur Zamarin
2024-08-02 19:09 ` matoro
2024-08-04 18:30 ` Andreas K. Huettel [this message]
2024-08-04 22:39   ` Robin H. Johnson
2024-08-05 12:29     ` Andreas K. Huettel
2024-08-05  6:44   ` [gentoo-project] " Ulrich Mueller

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=10508417.nUPlyArG6x@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@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