From: Michael Orlitzky <mjo@gentoo.org>
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, 08 Feb 2021 07:27:04 -0500 [thread overview]
Message-ID: <21900a2c5a585c3eba1c8a001d5e2229de819d6e.camel@gentoo.org> (raw)
In-Reply-To: <b1cd5b3e12cc40a30282293e1197b03f3ced8199.camel@gentoo.org>
On Mon, 2021-02-08 at 12:19 +0100, Michał Górny wrote:
>
> 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.
>
Not only that, but you will be dropping support for at least two of my
machines that are literally incapable of building the 10+ GiB bundled
rust package due to the amount of disk space and RAM required.
next prev parent reply other threads:[~2021-02-08 12:27 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 [this message]
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
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=21900a2c5a585c3eba1c8a001d5e2229de819d6e.camel@gentoo.org \
--to=mjo@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