From: "Ludovic Courtès" <ludo@gnu.org>
To: Reily Siegel <mail@reilysiegel.com>
Cc: 56439-done@debbugs.gnu.org
Subject: bug#56439: [PATCH] gnu: home: Add Guix channels service.
Date: Tue, 12 Jul 2022 00:07:38 +0200 [thread overview]
Message-ID: <87h73ni9qt.fsf_-_@gnu.org> (raw)
In-Reply-To: <87v8s3n6pj.fsf@reilysiegel.com> (Reily Siegel's message of "Wed, 29 Jun 2022 17:05:26 -0400")
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
Hi,
Reily Siegel <mail@reilysiegel.com> skribis:
> * gnu/home/services/guix.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add guix.scm.
> * doc/guix.texi: Add documentation for home-channels-service.
Neat! Applied with the cosmetic changes below.
> +(define (channels-xdg-files channels)
> + `(("guix/channels.scm"
> + ,(plain-file
> + "channels.scm"
> + (call-with-output-string
> + (lambda (port)
> + (pretty-print (cons 'list (map channel->code channels)) port)))))))
The downside with this approach is that it doesn’t let you have a
sophisticated ‘channels.scm’ file, for instance one that calls
‘channel-with-substitutes-available’ (info "(guix) Channels with
Substitutes").
All in all, I think that’s an acceptable limitation. Someone willing to
write arbitrary code to ‘channels.scm’ can “roll their own” and extend
‘home-xdg-configuration-files-service-type’ similarly.
Thanks,
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1052 bytes --]
diff --git a/doc/guix.texi b/doc/guix.texi
index 1f49d9bd6a..637a2cf744 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -40083,14 +40083,14 @@ user-specific Guix configuration.
@defvr {Scheme Variable} home-channels-service-type
This is the service type for managing
-@file{$XGG_CONFIG_HOME/guix/channels.scm}, the file which controls the
-channels recieved on @command{guix pull}. Its associated value is a list
+@file{$XDG_CONFIG_HOME/guix/channels.scm}, the file that controls the
+channels recieved on @command{guix pull}. Its associated value is a list
of @code{channel} records, defined in the @code{(guix channels)} module.
Generally, it is better to extend this service than to directly
configure it, as its default value is the default guix channel(s)
defined by @code{%default-channels}. If you configure this service
-directly, be sure to include a guix channel. See @ref{Specifying
+directly, be sure to include a guix channel. @xref{Specifying
Additional Channels} and @ref{Using a Custom Guix Channel} for more
details.
next prev parent reply other threads:[~2022-07-11 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 21:05 [bug#56439] [PATCH] gnu: home: Add Guix channels service Reily Siegel
2022-06-29 21:05 ` [bug#56439] [PATCH v2] " Reily Siegel
2022-06-29 21:05 ` [bug#56439] [PATCH v3] " Reily Siegel
2022-07-11 22:07 ` Ludovic Courtès [this message]
2022-07-08 6:54 ` [bug#56439] [PATCH] " ( via Guix-patches via
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h73ni9qt.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=56439-done@debbugs.gnu.org \
--cc=mail@reilysiegel.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.