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
Cc: gentoo-project@lists.gentoo.org, "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: [gentoo-dev] [Proposal] Split arch keywords for ppc64 & riscv
Date: Mon, 05 Aug 2024 14:29:51 +0200	[thread overview]
Message-ID: <8584278.lOV4Wx5bFT@kona> (raw)
In-Reply-To: <robbat2-20240804T223716-487177815Z@orbis-terrarum.net>

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

Am Montag, 5. August 2024, 00:39:13 CEST schrieb Robin H. Johnson:

> > 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.
> How do we identify something that was labelled as ppc64 and was
> pre-split, vs something that is post-split, and ONLY supposed PPC64 big
> endian, and NOT ppc64le.

Different profile selection (already now, ppc64 and ppc64le are different
profile trees).

> Under this proposal, both of variants would have KEYWORDS="ppc64".
> 
> What if the ppc64 splits into ppc64be & ppc64le to be extremely clear?
> 
> ...
> > Step 8: Remove all riscv keywords (no 64 or 32)
> > 
> > Step 9: Remove riscv as arch.
> Remove ppc64 without le/be suffixes.

Possible but more work...

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

  reply	other threads:[~2024-08-05 12:30 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
2024-08-04 22:39   ` Robin H. Johnson
2024-08-05 12:29     ` Andreas K. Huettel [this message]
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=8584278.lOV4Wx5bFT@kona \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=robbat2@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