ryan77627/guix
1
0
Fork 0
mirror of https://git.in.rschanz.org/ryan77627/guix.git synced 2024-12-25 05:48:07 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: Clarify that `guix-build' really is for developers.

Browse source 
* doc/guix.texi (Invoking guix-build): Make it clear that `guix-build'
  doesn't access the user's profile, and add cross-ref to `guix-package'.
  Suggested by Nikita Karetnikov <nikita@karetnikov.org>.
This commit is contained in:
Ludovic Courtès 2013-01-23 16:45:36 +01:00
parent 6e4da6ead1
commit 6798a8e485
1 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/guix.texi
View file

@ -982,8 +982,12 @@ space.
@section Invoking @command{guix-build} @section Invoking @command{guix-build}
The @command{guix-build} command builds packages or derivations and The @command{guix-build} command builds packages or derivations and
their dependencies, and prints the resulting store paths. It is mainly their dependencies, and prints the resulting store paths. Note that it
useful for distribution developers. The general syntax is: does not modify the user's profile---this is the job of the
@command{guix-package} command (@pxref{Invoking guix-package}). Thus,
it is mainly useful for distribution developers.
The general syntax is:
@example @example
guix-build @var{options} @var{package-or-derivation}@dots{} guix-build @var{options} @var{package-or-derivation}@dots{}
@ -1015,7 +1019,7 @@ Build the packages' source derivations, rather than the packages
themselves. themselves.
For instance, @code{guix-build -S gcc} returns something like For instance, @code{guix-build -S gcc} returns something like
@file{/nix/store/xxx-gcc-4.7.2.tar.bz2}, which is GCC's source tarball. @file{/nix/store/@dots{}-gcc-4.7.2.tar.bz2}, which is GCC's source tarball.
@item --system=@var{system} @item --system=@var{system}
@itemx -s @var{system} @itemx -s @var{system}