From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Moving more architectures to ~arch only
Date: Fri, 15 Oct 2021 09:54:22 +0300 [thread overview]
Message-ID: <46893875-a6b4-f8bc-13bf-f1bd46f3ae5c@gentoo.org> (raw)
In-Reply-To: <827b86fa2639792ddc8f016601d3ee374d186619.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1390 bytes --]
On 14.10.2021 20.10, Michał Górny wrote:
> On Thu, 2021-10-14 at 15:40 +0200, Marek Szuba wrote:
>> Dear everyone,
>>
>> Following some private discussions, I feel quite strongly now that it
>> would both considerably improve certain processes and make our use of
>> limited manpower more efficient were we to further reduce the number of
>> stable arches in Gentoo Linux. Specifically, I propose to drop
>> - hppa,
>> - ppc,
>> - sparc,
>> - x86
>> to ~arch-only status.
>>
Yes please. Still confused why people by default push KEYWORDS="~amd64
~x86", but I guess they're the most compatible with each other.
>
> On one hand, I fully realize that these platforms are a hassle (hppa
> and x86 especially). On the other hand, I wouldn't want to basically go
> tell Dakon "sorry, you're doing a good job but we've arbitrarily decided
> it's not worth your effort".
Isn't this just strengthening the point; there's one guy behind all work ;)
>
> While we're discussing it, maybe we should start by defining a clear
> criteria for platform support tiers? Like: what are the requirements
> for a platform to maintain stable keywords? Then the decisions could
> look less arbitrary, and people would have a clear way of knowing what
> they need to do if they wish the platform to continue having stable
> keywords.
>
++
-- juippis
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2021-10-15 6:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 13:40 [gentoo-dev] [RFC] Moving more architectures to ~arch only Marek Szuba
2021-10-14 16:08 ` Roy Bamford
2021-10-14 17:10 ` Michał Górny
2021-10-15 6:54 ` Joonas Niilola [this message]
2021-10-15 7:20 ` Agostino Sarubbo
2021-10-15 11:59 ` Mikhail Koliada
2021-10-15 21:40 ` Rolf Eike Beer
2021-10-16 6:17 ` Michał Górny
2021-11-04 18:56 ` Rolf Eike Beer
2021-10-16 21:14 ` William Hubbs
2021-10-18 0:25 ` Thomas Deutschmann
2021-10-18 1:08 ` John Helmert III
2021-10-18 15:09 ` Thomas Deutschmann
2021-10-18 17:07 ` Michał Górny
2021-10-19 15:36 ` Thomas Deutschmann
2021-10-18 17:32 ` Rolf Eike Beer
2021-11-04 18:08 ` Marek Szuba
2021-10-18 0:50 ` Sam James
2021-10-18 0:54 ` Sam James
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=46893875-a6b4-f8bc-13bf-f1bd46f3ae5c@gentoo.org \
--to=juippis@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