diff options
author | Alex Kost <alezost@gmail.com> | 2017-01-24 16:52:56 +0300 |
---|---|---|
committer | Alex Kost <alezost@gmail.com> | 2017-01-28 12:40:58 +0300 |
commit | f31f1acac2efb4bc6558b604a07b56f826423177 (patch) | |
tree | 412460d57f796ed922a16bce23263a908db9abdd /doc | |
parent | aaf111a2c4e260108aaae6b2de6eb058b005ebba (diff) |
doc: Fix typos.
* doc/guix.texi: Use "@" for package specifications.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/guix.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/guix.texi b/doc/guix.texi index 19d7f28dc2..719ebd917a 100644 --- a/doc/guix.texi +++ b/doc/guix.texi @@ -4511,7 +4511,7 @@ guix build --quiet --keep-going \ @var{package-or-derivation} may be either the name of a package found in the software distribution such as @code{coreutils} or -@code{coreutils-8.20}, or a derivation such as +@code{coreutils@8.20}, or a derivation such as @file{/gnu/store/@dots{}-coreutils-8.19.drv}. In the former case, a package with the corresponding name (and optionally version) is searched for among the GNU distribution modules (@pxref{Package Modules}). @@ -5671,7 +5671,7 @@ single output for a package that could easily be split (@pxref{Packages with Multiple Outputs}). Such are the typical issues that @command{guix size} can highlight. -The command can be passed a package specification such as @code{gcc-4.8} +The command can be passed a package specification such as @code{gcc@4.8} or @code{guile:debug}, or a file name in the store. Consider this example: |