Hello Ricardo,

Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. okt. 19., P
9:10):

>
> Hi Laura,
>
> > with guix environment --pure guix --ad-hoc coreutils findutils which (or
> -C)
> > I get, the output:
> > Command 'lesspipe' is available in the following places
> >  * /bin/lesspipe
> >  * /usr/bin/lesspipe
> > The command could not be located because '/bin:/usr/bin' is not
> > included in the PATH environment variable.
> > lesspipe: command not found
>
> This is because your shell initialization code (e.g. to set up the
> prompt) refers to lesspipe.  You can ignore this or remove the fancy
> initialization.
>
> > There, I run which guix and get:
> > which: no guix in
> >
> (/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/bin:/gnu/store/khk3lpx1li9y5zxzdppn9wi4n5g1qsgs-profile/sbin)
>
> That’s because “--pure” resets the PATH; that’s by design.  The only
> problem you have is that your Guix is located elsewhere.  But why do you
> need Guix itself inside of an environment to build Guix?
>
> The point of using “guix environment --pure guix” is only to enter a
> clean environment containing everything you need to build Guix from
> source.  So once you’re inside of this environment you can run the
> bootstrap and configure scripts, and run make to compile the sources.
>
> To *use* that Guix you just built you need to use “./pre-inst-env guix”
> from the source directory.
>
> > The closest I got was by setting:
> > PATH=$PATH:/usr/bin/:/bin
> > PATH=$PATH:/usr/local/bin
>
> This defeats the purpose of using “--pure” as these directories contain
> all sorts of things on a foreign distro, so you lose control over the
> environment.
>

Sorry, my bad, I missed that.


> --
> Ricardo
>
g_bor

>