public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fwd: [Python-Dev] Move support of legacy platforms/architectures outside Python
Date: Tue, 23 Feb 2021 09:11:52 +0100	[thread overview]
Message-ID: <327637551a9f22887bfbc1cf90fab56494aa4c20.camel@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr-B4Sz8+83zrhgxii_iLVsuTaQbhp5hjr+BoeVQds59ww@mail.gmail.com>

On Mon, 2021-02-22 at 22:16 -0800, Alec Warner wrote:
> So my question is basically, how much does Gentoo care about these
> ports? Should we be funding ports of rust to these arches (assuming
> that would continue ensure gentoo works on those arches.)

I think it's too early to say.  So far Python devs have not admitted any
relevance between Python supported architectures and Rust supported
architectures.  It is still possible that they would wish to block minor
architectures even if Rust were ported there.

On the other hand, what we need right now is a major effort towards
making Rust installable on the Gentoo architectures that are supported
by Rust upstream.  Maybe our Rust developers would use some funding to
be able to dedicate more time into it.

-- 
Best regards,
Michał Górny




      reply	other threads:[~2021-02-23  8:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABqyc3zVU0rLzcPA_vwdnDp3oKLP0HnMuDN6VNPwWpfY-X38hQ@mail.gmail.com>
2021-02-21 13:01 ` [gentoo-dev] Fwd: [Python-Dev] Move support of legacy platforms/architectures outside Python Michał Górny
2021-02-21 13:28   ` Aisha Tammy
2021-02-22  1:32   ` Joshua Kinard
2021-02-22  8:30     ` Michał Górny
2021-02-23  6:16   ` Alec Warner
2021-02-23  8:11     ` Michał Górny [this message]

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=327637551a9f22887bfbc1cf90fab56494aa4c20.camel@gentoo.org \
    --to=mgorny@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