public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: WANG Xuerui <i.gentoo@xen0n.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port
Date: Tue, 24 Aug 2021 11:30:05 +0800	[thread overview]
Message-ID: <417f6b30-5af4-da58-9d3d-c081a3d366e5@xen0n.name> (raw)
In-Reply-To: <ufsvfnp3k@gentoo.org>

On 8/12/21 14:39, Ulrich Mueller wrote:

>>>>>> On Thu, 12 Aug 2021, Michał Górny wrote:
>> On Thu, 2021-08-12 at 09:21 +0800, WANG Xuerui wrote:
>>> I would say this is mostly aesthetic matter, because we have equally
>>> long ARCH names like "microblaze" or "openrisc" too. From a user's
>>> perspective I'd personally prefer "loong" to save some typing, but
>>> "loongarch" wouldn't hurt that much either.
>> I think following upstream (i.e. "loongarch" convention) is better.
>> We have already caused some mess with custom names like "arm64".
> Can we please keep these identifiers short? Currently all ARCH names are
> 5 characters at most (except prefix, of course). The total length of the
> KEYWORDS line isn't the main issue here, but tools like eshowkw or
> tables in the various web interfaces.
>
> It is also in GLEP 53 if you need a formal reference:
> "Note that no limit on the length of both fields in the keyword are
> imposed. However, we cannot overemphasize our preference to keep
> keywords small and sensible."

It seems the discussion has gone quiet for a while now, so I take that 
we choose ARCH=loong over ARCH=loongarch according to GLEP 53?

If that doesn't receive much objection, I'll prepare and send the first 
few eclass patches soon.

> Ulrich


  reply	other threads:[~2021-08-24  3:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 16:39 [gentoo-dev] [RFC] Plans for a Gentoo/LoongArch port WANG Xuerui
2021-08-11 18:13 ` William Hubbs
2021-08-12  1:21   ` WANG Xuerui
2021-08-12  6:00     ` Michał Górny
2021-08-12  6:39       ` Ulrich Mueller
2021-08-24  3:30         ` WANG Xuerui [this message]
2021-08-24  8:46           ` Ulrich Mueller
2021-08-24 10:01             ` WANG Xuerui
2021-08-24 12:17               ` Ulrich Mueller
2021-08-12  9:55 ` Yixun Lan
2021-08-13  5:56   ` WANG Xuerui
2021-10-07 12:46 ` WANG Xuerui

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=417f6b30-5af4-da58-9d3d-c081a3d366e5@xen0n.name \
    --to=i.gentoo@xen0n.name \
    --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