public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alessandro Barbieri <lssndrbarbieri@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] dev-python/cryptography to use rust, effectively killing alpha, hppa, ia64, m68k, s390
Date: Mon, 8 Feb 2021 18:56:00 +0100	[thread overview]
Message-ID: <CACfyCdXE7CJFj1WDeE2OYFwh_949gMpCe8S=yx_7JBHUsAvjZQ@mail.gmail.com> (raw)
In-Reply-To: <b1cd5b3e12cc40a30282293e1197b03f3ced8199.camel@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2186 bytes --]

Il Lun 8 Feb 2021, 12:19 Michał Górny <mgorny@gentoo.org> ha scritto:

> Hi,
>
> FYI the developers of dev-python/cryptography decided that Rust is going
> to be mandatory for 1.5+ versions.  It's unlikely that they're going to
> provide LTS support or security fixes for the old versions.
>
> Since cryptography is a very important package in the Python ecosystem,
> and it is an indirect dependency of Portage, this means that we will
> probably have to entirely drop support for architectures that are not
> supported by Rust.
>
> According to upstream platform support information [1], this probably
> means (eventually) entirely removing the following architectures:
> - alpha (stable)
> - hppa (stable)
> - ia64 (stable)
> - m68k (exp)
> - s390 (except for s390x, exp)
>
> Furthermore, the Gentoo Rust packages are missing support
> for the following platforms, apparently supported upstream:
> - mips (exp)
> - ppc (32) (stable)
> - sparc (stable)
> - s390x (exp)
> - riscv (stable)
>
> Apparently it's non-trivial to bootstrap Rust on these platforms,
> so it's unclear when Gentoo is going to start providing Rust on them.
>
> I've raised a protest on the cryptography bug tracker [2] but apparently
> upstream considers Rust's 'memory safety' more important than ability to
> actually use the package.
>
> Honestly, I don't think it likely that Rust will gain support for these
> platforms.  This involves a lot of work, starting with writing a new
> LLVM backend and getting it accepted (getting new code into LLVM is very
> hard unless you're doing that on behalf one of the big companies).  You
> can imagine how much effort that involves compared to rewriting the new
> code from Cryptography into C.
>
> If we can't convince upstream, I'm afraid we'll either have to drop
> these architectures entirely or fork Cryptography.
>
>
> [1] https://doc.rust-lang.org/nightly/rustc/platform-support.html
> [2] https://github.com/pyca/cryptography/issues/5771
>
> --
> Best regards,
> Michał Górny
>

Should we shed tears for those legacy architectures or move forward? Does
anyone really use them in production?

>

[-- Attachment #2: Type: text/html, Size: 3051 bytes --]

  parent reply	other threads:[~2021-02-08 17:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 11:19 [gentoo-dev] dev-python/cryptography to use rust, effectively killing alpha, hppa, ia64, m68k, s390 Michał Górny
2021-02-08 11:27 ` Pacho Ramos
2021-02-08 11:30 ` James Le Cuirot
2021-02-08 11:44 ` Sam James
2021-02-08 12:27 ` Michael Orlitzky
2021-02-08 12:37   ` Joonas Niilola
2021-02-08 17:53 ` Brian Evans
2021-02-08 17:59   ` Joonas Niilola
2021-02-08 18:34   ` Michał Górny
2021-02-08 18:35   ` Brian Evans
2021-02-09  3:37     ` Mike Gilbert
2021-02-08 17:56 ` Alessandro Barbieri [this message]
2021-02-08 18:02   ` Alec Warner
2021-02-08 19:04     ` Aaron Bauman
2021-02-08 18:35   ` Michał Górny
2021-02-09 15:19 ` Michał Górny
2021-02-10  0:51   ` Benda Xu
2021-02-10  1:15     ` Tim Harder
2021-02-11  0:37       ` Alexey Sokolov
2021-02-10  1:51     ` Michael Orlitzky
2021-02-10 21:57   ` Peter Stuge
2021-02-10 22:49     ` Mike Gilbert
2021-02-10 23:11       ` Peter Stuge

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='CACfyCdXE7CJFj1WDeE2OYFwh_949gMpCe8S=yx_7JBHUsAvjZQ@mail.gmail.com' \
    --to=lssndrbarbieri@gmail.com \
    --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