unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: "Ludovic Courtès" <ludovic.courtes@inria.fr>, 48564@debbugs.gnu.org
Subject: bug#48564: ‘channel-with-substitutes-available’ makes assumptions about job names
Date: Thu, 27 May 2021 22:34:05 +0200	[thread overview]
Message-ID: <86o8cvncg2.fsf@gmail.com> (raw)
In-Reply-To: <87bl8x60lq.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 26 May 2021 16:17:21 +0200")

Hi,

On Wed, 26 May 2021 at 16:17, Mathieu Othacehe <othacehe@gnu.org> wrote:

> (channels-with-substitutes-available
>  (list %default-guix-channel
>        (channel
>         (name 'guix-hpc)
>         (url "https://gitlab.inria.fr/guix-hpc/guix-hpc.git")))
>  (list "https://ci.guix.gnu.org"
>        "https://guix.bordeaux.inria.fr")
>  (specs "master" "guix-hpc"))

FWIW, I do not know if ’channels-with-substitutes-available’ should take
a list of channels, but it should take a list of substitute servers.
For instance, the user should be allowed to provide (list
"https://ci.guix.gnu.org" "https://bayfront.guix.gnu.org") for the
channel %default-guix-channel.  And the default should be:

        (channels-with-substitutes-available
          %default-guix-channel
          %default-substitute-urls)

Then, for multi-channels, the substitute servers should be a list of
list, IMHO.  Although, in practise, currently, there is less substitute
servers than channels. ;-)


Cheers,
simon




      parent reply	other threads:[~2021-05-27 20:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 12:58 bug#48564: ‘channel-with-substitutes-available’ makes assumptions about job names Ludovic Courtès
2021-05-21 13:28 ` Mathieu Othacehe
2021-05-21 14:30   ` Ludovic Courtès
2021-05-26 14:17     ` Mathieu Othacehe
2021-05-27  9:20       ` Ludovic Courtès
2021-05-27 20:34       ` zimoun [this message]

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=86o8cvncg2.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=48564@debbugs.gnu.org \
    --cc=ludovic.courtes@inria.fr \
    --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).