From: Richard Sent <richard@freakingpenguin.com>
To: guix-devel@gnu.org, Ricardo Wurmus <rekado@elephly.net>,
Leo Famulari <leo@famulari.name>
Cc: 67535@debbugs.gnu.org, Efraim Flashner <efraim@flashner.co.il>
Subject: Re: Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux]
Date: Mon, 29 Jul 2024 11:00:36 -0400 [thread overview]
Message-ID: <A882707A-3035-4986-B630-23CDFD20B6C7@freakingpenguin.com> (raw)
In-Reply-To: <87sevsxtqg.fsf@elephly.net>
>> In terms of side-stepping the question, do we have enough x86_64
>> hardware to continue to support i686 without degrading support for
>> x86_64? (I ask this seriously, although I'm pretty certain the answer is
>> we're well covered on that front.)
>
>Support does not just mean dedicating build cycles to doomed builds, but
>also dedicating people's time to wade through hundreds of failures for
>little gain. Perhaps our time is better spent supporting architectures
>that still have a future.
>
For consideration, I know at least one 3rd-party channel relies on being able to create a multiarch container containing i686 packages. I'll refrain from linking since it packages nonfree software. This is an example where keeping an old architecture around is more complicated than simply counting the number of active machines using said architecture.
Perhaps we could tally the number of substitutes served for supported architectures and use that as our metric for liveliness.
next prev parent reply other threads:[~2024-07-29 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZWelMw84qtyRxxS6@jasmine.lan>
[not found] ` <ZXBoKfOxrITAuOoF@3900XT>
2024-07-26 18:51 ` Does anyone use i686-linux? [was Re: bug#67535: ci.guix.gnu.org 'Cannot allocate memory' while building for i686-linux] Leo Famulari
2024-07-26 20:17 ` Kaelyn
2024-07-28 21:49 ` Efraim Flashner
2024-07-29 12:33 ` Ricardo Wurmus
2024-07-29 15:00 ` Richard Sent [this message]
2024-07-30 0:01 ` Leo Famulari
2024-07-30 1:21 ` Richard Sent
2024-07-30 14:39 ` Leo Famulari
2024-08-01 23:51 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-07-30 15:18 ` Efraim Flashner
2024-07-30 21:02 ` bug#67535: " André Batista
2024-08-01 20:12 ` Leo Famulari
2024-08-02 8:36 ` Ricardo Wurmus
2024-08-02 19:34 ` bug#67535: " André Batista
2024-09-05 9:42 ` Ricardo Wurmus
2024-09-05 23:52 ` André Batista
2024-08-12 14:03 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A882707A-3035-4986-B630-23CDFD20B6C7@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=67535@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).