From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: Guix Devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: armhf-linux substitutes
Date: Wed, 17 Mar 2021 18:28:56 +0100 [thread overview]
Message-ID: <87pmzx1yg7.fsf_-_@gnu.org> (raw)
In-Reply-To: <YE+kHMia9TflbQnZ@jasmine.lan> (Leo Famulari's message of "Mon, 15 Mar 2021 14:14:52 -0400")
Hi,
Leo Famulari <leo@famulari.name> skribis:
> On Mon, Mar 15, 2021 at 05:55:21PM +0100, Ludovic Courtès wrote:
>> > The architecture armf will not be included.
>>
>> Wait wait, I missed that. What happened? I think we should include it,
>> even if substitute availability remains low.
>
> I had asked about the status of the armhf branch on #guix when a few of
> us were trying to "tie up loose ends" for this release.
>
> I don't have an opinion one way or the other, but since we are not
> building substitutes for it at all, we should include in the release
> announcement a clear description of the level of support that users can
> expect.
Right, we could adjust the text in the “GNU Distribution” node of the
manual (we did that before when mips64el-linux was supported without
substitutes.)
Mathieu, what’s preventing us from doing armhf-linux builds again? We
could use the OverDrives for that (with an upper bound though), along
with the SBCs in machines-for-berlin.scm.
That won’t be enough to keep up, so perhaps we’ll have to restrict
armhf-linux builds to the “core” subset or the release-manifest.scm.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2021-03-17 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 15:00 Release 1.2.1: timeline zimoun
2021-03-15 16:55 ` Ludovic Courtès
2021-03-15 17:08 ` Vincent Legoll
2021-03-15 18:14 ` Leo Famulari
2021-03-15 20:15 ` Vincent Legoll
2021-03-15 20:27 ` Leo Famulari
2021-03-17 17:28 ` Ludovic Courtès [this message]
2021-03-17 18:56 ` armhf-linux substitutes zimoun
2021-03-29 7:21 ` Mathieu Othacehe
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=87pmzx1yg7.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=othacehe@gnu.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.
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).