From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 45104@debbugs.gnu.org
Subject: [bug#45104] pull: Add a "with-substitutes" option.
Date: Sun, 31 Jan 2021 17:18:55 +0100 [thread overview]
Message-ID: <87eei1nkpc.fsf@gnu.org> (raw)
In-Reply-To: <87y2gbj25d.fsf@gnu.org> (Mathieu Othacehe's message of "Fri, 29 Jan 2021 14:36:30 +0100")
Hi!
Mathieu Othacehe <othacehe@gnu.org> skribis:
> From 31dad6456825a329ba0f07c95e3e99258d186a8f Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe <othacehe@gnu.org>
> Date: Fri, 29 Jan 2021 13:48:44 +0100
> Subject: [PATCH v2] guix: channels: Introduce
> "channel-with-substitutes-available".
>
> * guix/channels.scm (find-latest-commit-with-substitutes,
> channel-with-substitutes-available): New procedures.
> * guix/scripts/pull.scm (guix-pull): Move "channel-list" call inside the
> %current-system parameter scope.
> * doc/guix.texi (Channels with substitutes): New section.
Yay!
> +@node Channels with substitutes
> +@section Channels with substitutes
Should be “Channels With Substitutes”
> +When running @command{guix pull}, Guix will first compile the
> +definitions of every available package. This is an expensive operation
> +for which substitutes (@pxref{Substitutes}) may be available. The
> +following snippet in @file{channels.scm} will ensure that @command{guix
> +pull} uses the latest commit with available substitutes for the package
> +definitions. This is done by querying the continuous integration
^
I’d replace the period with a colon and insert the example right here.
> +server at @url{https://ci.guix.gnu.org}.
> +
> +Be careful, this does not mean that all the packages that you will
s/Be careful,/Note that/
> +install after running @command{guix pull} will have available
> +substitutes. It only ensures that @command{guix pull} will not try to
> +compile package definitions. This is particularly useful when using
> +machines with limited resources.
> +
> +@lisp
> +(list
> + (channel-with-substitutes-available
^
Nipick: maybe move on the previous line.
> (define-module (guix channels)
> #:use-module (git)
> + #:use-module (guix ci)
Could we instead move these two procedures to (guix ci), with an
#:autoload for (guix channels), so that (guix channels) remains focused
on core functionality?
It does mean that in the example above we need to add an explicit
(use-modules (guix ci)).
Otherwise LGTM, thanks!
Ludo’.
next prev parent reply other threads:[~2021-01-31 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 15:39 [bug#45104] pull: Add a "with-substitutes" option Mathieu Othacehe
2020-12-07 17:05 ` zimoun
2020-12-08 19:17 ` Christopher Baines
2020-12-14 11:05 ` Ludovic Courtès
2020-12-14 11:39 ` zimoun
2020-12-15 10:30 ` Mathieu Othacehe
2020-12-15 12:51 ` zimoun
2020-12-15 10:24 ` Mathieu Othacehe
2020-12-15 22:03 ` Ludovic Courtès
2021-01-29 13:23 ` Mathieu Othacehe
2021-01-29 13:36 ` Mathieu Othacehe
2021-01-31 16:18 ` Ludovic Courtès [this message]
2021-01-31 17:37 ` bug#45104: " 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=87eei1nkpc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=45104@debbugs.gnu.org \
--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).