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 th
> On Sun, 04 Aug 2024, Andreas K Huettel wrote:
> 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.
Presumably this will also require eselect to be updated
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 keyw
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 precede
On 2024-08-02 15:05, Arthur Zamarin wrote:
Hi all
As continuation from previous arch changes and arch status [1], I want
to propose the next arch change for the near council meeting:
a. Splitting ppc64 keyword into ppc64 and ppc64le
Currently the ppc64 arch keyword matches both big endian (ppc
Hi all
As continuation from previous arch changes and arch status [1], I want
to propose the next arch change for the near council meeting:
a. Splitting ppc64 keyword into ppc64 and ppc64le
Currently the ppc64 arch keyword matches both big endian (ppc64ul) and
little endian (ppc64le). While ther
