mirror of
https://git.in.rschanz.org/ryan77627/guix.git
synced 2024-11-07 07:26:13 -05:00
doc: Improve wording and fix typos in "Features".
* doc/guix.texi (Features): Fix typos, and rephrase according to the suggestions of Alex Sassmannshausen <alex.sassmannshausen@gmail.com>.
This commit is contained in:
parent
2b902c3c46
commit
821b0015fa
1 changed files with 11 additions and 10 deletions
|
@ -396,24 +396,25 @@ own directory---something that resembles
|
||||||
|
|
||||||
Instead of referring to these directories, users have their own
|
Instead of referring to these directories, users have their own
|
||||||
@dfn{profile}, which points to the packages that they actually want to
|
@dfn{profile}, which points to the packages that they actually want to
|
||||||
use. That profile is normally stored in @code{$HOME/.guix-profile}, and
|
use. These profiles are stored within each user's home directory, at
|
||||||
each user has its own profile.
|
@code{$HOME/.guix-profile}.
|
||||||
|
|
||||||
For example, if @code{alice} installed GCC 4.7.2, then
|
For example, @code{alice} installs GCC 4.7.2. As a result,
|
||||||
@file{/home/alice/.guix-profile/bin/gcc} points to
|
@file{/home/alice/.guix-profile/bin/gcc} points to
|
||||||
@file{/nix/store/xxx-gcc-4.7.2/bin/gcc}; on the same machine, @code{bob}
|
@file{/nix/store/@dots{}-gcc-4.7.2/bin/gcc}. Now, on the same machine,
|
||||||
may have installed GCC 4.8.0, in which case its profile refers to these
|
@code{bob} had already installed GCC 4.8.0. The profile of @code{bob}
|
||||||
particular package installation. Both coexist, without any
|
simply continues to point to
|
||||||
interference.
|
@file{/nix/store/@dots{}-gcc-4.8.0/bin/gcc}---i.e., both versions of GCC
|
||||||
|
coexist on the same system without any interference.
|
||||||
|
|
||||||
The @command{guix-package} command is the central tool to manage
|
The @command{guix-package} command is the central tool to manage
|
||||||
packages. It operates on those per-user profiles, and can be used
|
packages (@pxref{Invoking guix-package}). It operates on those per-user
|
||||||
@emph{with normal user privileges}.
|
profiles, and can be used @emph{with normal user privileges}.
|
||||||
|
|
||||||
The command provides the obvious install, remove, and upgrade
|
The command provides the obvious install, remove, and upgrade
|
||||||
operations. Each invocation is actually a @emph{transaction}: either
|
operations. Each invocation is actually a @emph{transaction}: either
|
||||||
the specified operation succeeds, or nothing happens. Thus, if the
|
the specified operation succeeds, or nothing happens. Thus, if the
|
||||||
@command{guix-package} processed is terminated during the transaction,
|
@command{guix-package} process is terminated during the transaction,
|
||||||
or if a power outage occurs during the transaction, then the user's
|
or if a power outage occurs during the transaction, then the user's
|
||||||
profile remains in its previous state, and remains usable.
|
profile remains in its previous state, and remains usable.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue