Hi Alex, Alex Sassmannshausen <alex.sassmannshau...@gmail.com> skribis:
> Whilst reading the published manual on the GNU Guix website I came across the > following three sentences that could maybe be improved (their all in section > 3.1): > 'Instead of referring to these directories, users have their own profile, > which points to the packages that they actually want to use. That profile is > normally stored in $HOME/.guix-profile, and each user has its own profile. ' > Would probably sound better and read easier if it were: > 'Instead of referring to these directories, users each have their own > profile, which points to the packages that they actually want to use. These > profiles are stored within each user's own home directory, at > $HOME/.guix-profile.' Indeed. > The nextparagraph could be rewritten as (though maybe just unnecessary > rewording): > For example, alice installs GCC 4.7.2. As a result, gcc in her profile, > /home/alice/.guix-profile/bin/gcc would point to > /nix/store/xxx-gcc-4.7.2/bin/gcc. Now, on the same machine, bob had already > installed GCC 4.8.0. Bob's profile simply continues to point to > /nix/store/xxx-gcc-4.8.0/bin/gcc; i.e. both versions of GCC coexist on the > same system without any interference. Yes, makes sense. > Finally, what I think is a typ-o: > …if the guix-package processed is terminated… > should be > …if the guix-package process is terminated… Right. I’ve applied these suggestions in commit 821b001. > I also just now, when re-configuring with a different store directory, > noticed that there might be a typ-o in the localstatedir param example. It > currently says: > The default values are --with-store-dir=/nix/store and > --localstatedir=/nix/var. > But I think it should read > […] and --localstatedir=/var/nix. No, /nix/var is really what is meant here. > Hope this helps, let me know if it's better to provide this kind of thing in > a different fashion. The source of this document is the doc/guix.texi file in the source code repository. It’s more convenient if you send a patch against that file (ideally using the ‘git format-patch’ command), but it’s also helpful if you report typos like you did. Thanks! Ludo’.
