From: "Ludovic Courtès" <ludo@gnu.org>
To: 66577@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#66577] [PATCH 4/4] doc: cookbook: Add cross references to the manual regarding manifests.
Date: Mon, 16 Oct 2023 14:43:03 +0200 [thread overview]
Message-ID: <0a08f973a486c025453c98b1ab34cb4ffc24fc82.1697459606.git.ludo@gnu.org> (raw)
In-Reply-To: <cover.1697459606.git.ludo@gnu.org>
* doc/guix-cookbook.texi (The benefits of manifests)
(Reproducible profiles): Add cross-references.
---
doc/guix-cookbook.texi | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/doc/guix-cookbook.texi b/doc/guix-cookbook.texi
index 1259f6aac7..b1fe1b932f 100644
--- a/doc/guix-cookbook.texi
+++ b/doc/guix-cookbook.texi
@@ -3987,7 +3987,9 @@ Default profile
@node The benefits of manifests
@subsection The benefits of manifests
-Manifests are a convenient way to keep your package lists around and, say,
+Manifests let you @dfn{declare} the set of packages you'd like to have
+in a profile (@pxref{Writing Manifests,,, guix, GNU Guix Reference Manual}).
+They are a convenient way to keep your package lists around and, say,
to synchronize them across multiple machines using a version control system.
A common complaint about manifests is that they can be slow to install when they
@@ -4064,16 +4066,18 @@ Reproducible profiles
@itemize
@item
-a manifest,
+a manifest (@pxref{Writing Manifests,,, guix, GNU Guix Reference Manual});
@item
-a Guix channel specification.
+a Guix channel specification (@pxref{Replicating Guix,,, guix, GNU Guix
+Reference Manual}).
@end itemize
Indeed, manifests alone might not be enough: different Guix versions (or
different channels) can produce different outputs for a given manifest.
You can output the Guix channel specification with @samp{guix describe
---format=channels}.
+--format=channels} (@pxref{Invoking guix describe,,, guix, GNU Guix
+Reference Manual}).
Save this to a file, say @samp{channel-specs.scm}.
On another computer, you can use the channel specification file and the manifest
--
2.41.0
next prev parent reply other threads:[~2023-10-16 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 12:36 [bug#66577] [PATCH 0/4] Newcomer-oriented improvements to the manual and cookbook Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 1/4] doc: Move “System Troubleshooting Tips” below Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 2/4] doc: Mention Guix Home in “Getting Started” Ludovic Courtès
2023-10-18 16:19 ` Simon Tournier
2023-10-24 13:53 ` Ludovic Courtès
2023-10-16 12:43 ` [bug#66577] [PATCH 3/4] doc: cookbook: Suggest ‘guix shell’ as an alternative to multiple profiles Ludovic Courtès
2023-10-16 12:43 ` Ludovic Courtès [this message]
2023-10-17 10:05 ` [bug#66577] [PATCH 0/4] Newcomer-oriented improvements to the manual and cookbook Mathieu Othacehe
2023-10-18 16:34 ` Simon Tournier
2023-10-24 16:12 ` bug#66577: " 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=0a08f973a486c025453c98b1ab34cb4ffc24fc82.1697459606.git.ludo@gnu.org \
--to=ludo@gnu.org \
--cc=66577@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).