From: Karl Hallsby <karl@hallsby.com>
To: 60392@debbugs.gnu.org
Cc: Karl Hallsby <karl@hallsby.com>
Subject: [bug#60392] [PATCH 2/2] doc: give example of when to use describe in .guix-channel file
Date: Wed, 28 Dec 2022 17:40:59 -0600 [thread overview]
Message-ID: <2179575812ab418c3a98f102d2d4448b64c20b87.1672270580.git.karl@hallsby.com> (raw)
In-Reply-To: <cover.1672270580.git.karl@hallsby.com>
---
doc/guix.texi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guix.texi b/doc/guix.texi
index 7c02e2d392..cb9d1d685c 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5620,6 +5620,11 @@ The modules must be @b{underneath} the specified directory, as the
defined as @code{(define-module (gnu packages fun))} must be located at
@code{base/gnu/packages/fun.scm}.
+Doing this allows for only parts of a repository to be used as a
+channel, as Guix looks for valid Guile modules when pulling. For
+instance, by default @command{guix deploy} machine configuration files
+are not valid Guile modules, making @command{guix pull} fail.
+
@node Declaring Channel Dependencies
@section Declaring Channel Dependencies
--
2.37.1
next prev parent reply other threads:[~2022-12-28 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 23:39 [bug#60392] [PATCH 0/2] [DOCUMENTATION]: describe .guix-channel directory field Karl Hallsby
2022-12-28 23:40 ` [bug#60392] [PATCH 1/2] doc: describe format of channel that uses " Karl Hallsby
2022-12-28 23:40 ` Karl Hallsby [this message]
2022-12-29 19:02 ` bug#60392: [PATCH 0/2] [DOCUMENTATION]: describe .guix-channel " Ricardo Wurmus
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=2179575812ab418c3a98f102d2d4448b64c20b87.1672270580.git.karl@hallsby.com \
--to=karl@hallsby.com \
--cc=60392@debbugs.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).