me/guix
Archived
1
0
Fork 0
Code Activity

doc: cookbook: Fix quotes.

Browse source 
* doc/guix-cookbook.texi (Basic setup with manifests):
(Default profile):
(The benefits of manifests): Use proper quotes in regular texts.
This commit is contained in:
Nicolas Goaziou 2020-04-25 23:10:16 +02:00
parent 5cca16968e
commit 128b136ec6
No known key found for this signature in database
GPG key ID: DA00B4F048E92F2D
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/guix-cookbook.texi
View file

@ -1791,8 +1791,8 @@ where we will store our profiles in the rest of this article.
Placing all your profiles in a single directory, with each profile getting its Placing all your profiles in a single directory, with each profile getting its
own sub-directory, is somewhat cleaner. This way, each sub-directory will own sub-directory, is somewhat cleaner. This way, each sub-directory will
contain all the symlinks for precisely one profile. Besides, "looping over contain all the symlinks for precisely one profile. Besides, ``looping over
profiles" becomes obvious from any programming language (e.g.@: a shell script) by profiles'' becomes obvious from any programming language (e.g.@: a shell script) by
simply looping over the sub-directories of @samp{$GUIX_EXTRA_PROFILES}. simply looping over the sub-directories of @samp{$GUIX_EXTRA_PROFILES}.
Note that it's also possible to loop over the output of Note that it's also possible to loop over the output of
@ -1926,7 +1926,7 @@ What about the default profile that Guix keeps in @file{~/.guix-profile}?
You can assign it the role you want. Typically you would install the manifest You can assign it the role you want. Typically you would install the manifest
of the packages you want to use all the time. of the packages you want to use all the time.
Alternatively, you could keep it "manifest-less" for throw-away packages Alternatively, you could keep it ``manifest-less'' for throw-away packages
that you would just use for a couple of days. that you would just use for a couple of days.
This way makes it convenient to run This way makes it convenient to run
@ -1957,7 +1957,7 @@ Manifests come with multiple benefits. In particular, they ease maintenance:
@itemize @itemize
@item @item
When a profile is set up from a manifest, the manifest itself is When a profile is set up from a manifest, the manifest itself is
self-sufficient to keep a "package listing" around and reinstall the profile self-sufficient to keep a ``package listing'' around and reinstall the profile
later or on a different system. For ad-hoc profiles, we would need to later or on a different system. For ad-hoc profiles, we would need to
generate a manifest specification manually and maintain the package versions generate a manifest specification manually and maintain the package versions
for the packages that don't use the default version. for the packages that don't use the default version.
@ -1994,7 +1994,7 @@ They can be manipulated in Scheme and passed to the various Guix @uref{https://e
It's important to understand that while manifests can be used to declare It's important to understand that while manifests can be used to declare
profiles, they are not strictly equivalent: profiles have the side effect that profiles, they are not strictly equivalent: profiles have the side effect that
they "pin" packages in the store, which prevents them from being they ``pin'' packages in the store, which prevents them from being
garbage-collected (@pxref{Invoking guix gc,,, guix, GNU Guix Reference Manual}) garbage-collected (@pxref{Invoking guix gc,,, guix, GNU Guix Reference Manual})
and ensures that they will still be available at any point in and ensures that they will still be available at any point in
the future. the future.