From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-dev] [Proposal] Split arch keywords for ppc64 & riscv
Date: Sun, 4 Aug 2024 22:39:13 +0000 [thread overview]
Message-ID: <robbat2-20240804T223716-487177815Z@orbis-terrarum.net> (raw)
In-Reply-To: <10508417.nUPlyArG6x@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Sun, Aug 04, 2024 at 08:30:57PM +0200, Andreas K. Huettel wrote:
> Hi Arthur,
>
> > a. Splitting ppc64 keyword into ppc64 and ppc64le
>
> > b. Splitting riscv keyword into riscv(64?) and riscv32
...
> 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.
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.
--
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation President & Treasurer
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1113 bytes --]
next prev parent reply other threads:[~2024-08-04 22:39 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 [this message]
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=robbat2-20240804T223716-487177815Z@orbis-terrarum.net \
--to=robbat2@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