Re: 2 (possible) problems in documentation

[Alex Kost <alezost@gmail.com>]

Alex Vong (2015-11-01 06:22 +0300) wrote:

> On 01/11/2015, Alex Kost <alezost@gmail.com> wrote:
>> Alex Vong (2015-10-31 14:27 +0300) wrote:
[...]
>>> 2. In
>>> <https://www.gnu.org/software/guix/manual/guix.html#Running-Guix-Before-It-Is-Installed>,
>>> it said "To that end, all the command-line tools can be used even if
>>> you have not run make install.". However, in the case of "guix pull",
>>> it is not true. Even if "guix pull" does run properly, it will not
>>> update the source tree you have downloaded, so you end up with running
>>> the original compiled version of Guix. Obviously, I was a victim :)
>>
>> Sorry, I don't understand what you mean here.  "guix pull" can't update
>> the source tree you downloaded.  It fetches the latest guix source,
>> compiles it, put it to the store and link "~/.config/guix/latest" to it.
>> Then the Guix code from this directory when you run "guix ..." commands.
>>
>> If you use the described "pre-inst-env" method, the code from the git
>> directory is used instead, and running "guix pull" doesn't effect
>> ".../pre-inst-env guix" commands in any way.  Here instead of "guix
>> pull" you use "git pull" and "make".
>>
> What I mean is "guix pull" only works after Guix is installed, so what
> the documentation says, "To that end, all the command-line tools can
> be used even if you have not run make install", is inaccurate. Should
> we note this in the documentation?

IMO it is accurate, because "./pre-inst-env guix pull" also works; it
just doesn't work the way you thought.  But if you find the
documentation confusing you are welcome to improve it :-)

-- 
Alex