[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
13/15: doc: Mention "guix home import" upfront.
From: |
guix-commits |
Subject: |
13/15: doc: Mention "guix home import" upfront. |
Date: |
Sat, 30 Oct 2021 18:52:37 -0400 (EDT) |
civodul pushed a commit to branch master
in repository guix.
commit 7711a6c3f41b0791f9fac60d31954f5ce478b7b8
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Sun Oct 31 00:16:44 2021 +0200
doc: Mention "guix home import" upfront.
* doc/guix.texi (Declaring the Home Environment): Mention "guix home
import".
---
doc/guix.texi | 27 +++++++++++++++++++++------
1 file changed, 21 insertions(+), 6 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 066971b..c78dbdc 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -35853,12 +35853,27 @@ still in an experimental stage, though.
@section Declaring the Home Environment
The home environment is configured by providing a
@code{home-environment} declaration in a file that can be passed to the
-@command{guix home} command (@pxref{Invoking guix home}). A simple
-setup can include Bash and a custom text configuration, like in the
-example below. Don't be afraid to declare home environment parts, which
-overlaps with your current dotfiles, before installing any configuration
-files, Guix Home will back up existing config files to a separate place
-in the home folder.
+@command{guix home} command (@pxref{Invoking guix home}). The easiest
+way to get started is by generating an initial configuration with
+@command{guix home import}:
+
+@example
+guix home import ~/src/guix-config
+@end example
+
+The @command{guix home import} command reads some of the ``dot files''
+such as @file{~/.bashrc} found in your home directory and copies them to
+the given directory, @file{~/src/guix-config} in this case; it also
+reads the contents of your profile, @file{~/.guix-profile}, and, based
+on that, it outputs a Home configuration that resembles your current
+configuration. You can dump that configuration to a file and you're
+ready to go!
+
+A simple setup can include Bash and a custom text configuration, like in
+the example below. Don't be afraid to declare home environment parts,
+which overlaps with your current dot files: before installing any
+configuration files, Guix Home will back up existing config files to a
+separate place in the home directory.
@quotation Note
It is highly recommended that you manage your shell or shells with Guix
- branch master updated (cf0abb6 -> c4ac8cf), guix-commits, 2021/10/30
- 10/15: home: import: Clarify "destination directory"., guix-commits, 2021/10/30
- 04/15: guix home: import: Don’t use 'slurp-file-gexp'., guix-commits, 2021/10/30
- 13/15: doc: Mention "guix home import" upfront.,
guix-commits <=
- 12/15: home: import: Avoid duplication of 'manifest->code'., guix-commits, 2021/10/30
- 14/15: doc: Avoid misuse of @ref., guix-commits, 2021/10/30
- 08/15: guix home: import: Call ‘local-file’ with ‘name’, guix-commits, 2021/10/30
- 05/15: guix home: import: Delete duplicate modules when importing., guix-commits, 2021/10/30
- 01/15: guix home: import: Make the user to specify a destination directory., guix-commits, 2021/10/30
- 03/15: guix home: import: Fix module name for Bash service., guix-commits, 2021/10/30
- 09/15: home: import: Compare procedures with 'eq?'., guix-commits, 2021/10/30
- 06/15: doc: Document the ‘guix home import’ subcommand., guix-commits, 2021/10/30
- 07/15: Add tests for ‘guix home import’., guix-commits, 2021/10/30
- 11/15: home: import: Factorize triplicated 'version-spec' procedure., guix-commits, 2021/10/30