unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated: gnu: sbcl: Update to 2.1.4.
Date: Sun, 2 May 2021 10:52:31 -0400	[thread overview]
Message-ID: <YI68r/xXlAoxIoub@jasmine.lan> (raw)
In-Reply-To: <87zgxdh30p.fsf@ambrevar.xyz>

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

On Sun, May 02, 2021 at 11:57:10AM +0200, Pierre Neidhardt wrote:
> Indeed, as far as I can remember we've always updated SBCL directly on
> master, because it's one of those exceptions.

Alright, I didn't know that. Let's keep the status quo in that case.
Maybe we should mention this kind of exception to the guidelines in the
manual. I want to revisit those guidelines after the upcoming release.

> What do you mean with "coordinate it in advance"?  Is there a better way
> to handle the process?

For example, we could make an sbcl-updates branch and build that in its
own Cuirass job. It makes it a little easier to schedule and manage the
computing resources used for a task. But if these packages are actually
cheap to build, then it's probably not necessary.

> Otherwise I can remove aarch64 from the list of supported systems in the
> SBCL package.

We try to avoid limiting the utility of packages just to work around
problems with the build farm (SBCL does build on real aarch64 hardware),
so it would be ideal if we could avoid this. I don't really know a good
way to deal with this particular problem.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-05-02 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210501115326.31478.20737@vcs0.savannah.gnu.org>
2021-05-02  3:23 ` branch master updated: gnu: sbcl: Update to 2.1.4 Leo Famulari
2021-05-02  9:57   ` Pierre Neidhardt
2021-05-02 14:52     ` Leo Famulari [this message]
2021-05-02 17:07       ` Pierre Neidhardt

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=YI68r/xXlAoxIoub@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).