From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <marius@gnu.org>
Cc: 42030@debbugs.gnu.org
Subject: [bug#42030] [PATCH] channels: Error out when the 'guix' channel lacks an introduction.
Date: Thu, 25 Jun 2020 11:29:07 +0200 [thread overview]
Message-ID: <87r1u3trx8.fsf@gnu.org> (raw)
In-Reply-To: <87d05o6ubc.fsf@gnu.org> (Marius Bakke's message of "Wed, 24 Jun 2020 23:13:43 +0200")
Hi,
Marius Bakke <marius@gnu.org> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> * guix/channels.scm (latest-channel-instance): Raise an error instead of
>> warning when 'guix is unauthenticated.
>> * tests/channels.scm ("latest-channel-instances, missing introduction for 'guix'"):
>> New test.
>
> The hunk in tests/channels.scm does not apply. :-) LGTM, anyway.
Ah, maybe because you were too fast: it depends on
a18d02def9862dfb9b7a5e3d5aa3b541b066d198, which I pushed yesterday.
> I think we should export %guix-channel-introduction, or alternatively
> add a %default-guix-channel that can be inherited, for easy access in
> custom channels.scm files. WDYT?
The idea was to expose only ‘%default-channels’, which leaves room for
the possibility of having multiple channels by default. I’d rather
avoid exposing the individual bits as that’s a bit of an additional
committment.
But note that the introduction of the “official” guix channel is
automatically added anyway (commit
c3f6f564e909ebefe752d24b325871a4e3a02d40).
Thanks for your feedback!
Ludo’.
next prev parent reply other threads:[~2020-06-25 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 12:57 [bug#42030] [PATCH] channels: Error out when the 'guix' channel lacks an introduction Ludovic Courtès
2020-06-24 21:13 ` Marius Bakke
2020-06-25 9:29 ` Ludovic Courtès [this message]
2020-06-29 11:47 ` Marius Bakke
2020-06-29 15:14 ` Ludovic Courtès
2020-07-25 15:05 ` Marius Bakke
2020-06-28 21:31 ` bug#42030: " 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=87r1u3trx8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42030@debbugs.gnu.org \
--cc=marius@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).