From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catonano Subject: Re: "--pure" won't work Date: Tue, 4 Oct 2016 23:33:53 +0200 Message-ID: References: <0b99763d20463819b869bb6cf7714942@hypermove.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0103e05c38a01d053e10d140 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56490) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1brXLY-0006c1-O5 for help-guix@gnu.org; Tue, 04 Oct 2016 17:33:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1brXLX-0001ID-4n for help-guix@gnu.org; Tue, 04 Oct 2016 17:33:56 -0400 In-Reply-To: <0b99763d20463819b869bb6cf7714942@hypermove.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Amirouche Boubekki Cc: help-guix , Help-Guix --089e0103e05c38a01d053e10d140 Content-Type: text/plain; charset=UTF-8 Amirouche, David, 2016-10-04 23:07 GMT+02:00 Amirouche Boubekki : > On 2016-10-04 22:42, Catonano wrote: > >> In exploring Culturia, here >> >> https://github.com/amirouche/Culturia/ [1] >> >> I reach this line >> >> guix environment --ad-hoc --pure guile-next >> >> > Both with and without --pure works on my side. I don't remember why I've > put --pure in the README. > > I use ubuntu 16.04.1, I have this in my ~/.zshrc > > export PATH="/home/amirouche/.guix-profile/bin":$PATH > export GUIX_LOCPATH=~/.guix-profile/lib/locale > export GUILE_LOAD_PATH="/home/amirouche/.guix-profile/share/guile/ > site/2.2${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH" > export GUILE_LOAD_COMPILED_PATH="/home/amirouche/.guix-profile/shar > e/guile/site/2.2${GUILE_LOAD_COMPILED_PATH:+:}$GUILE_LOAD_COMPILED_PATH" > export INFOPATH="/home/amirouche/.guix-profile/share/info${INFOPATH > :+:}$INFOPATH" > > Thanks to the both of you David's answer was a bit terse althought straight to the point Just to widen the discussion a bit, yes, in order to have basic commands in a "pure" environment, even ls, they need to be explicitly included (either with the --ad-hoc clause or because they're dependencies of some of the packages you're creating the env for) In fact guix environment --pure --ad-hoc guile-next --search-paths will show the "bin" that'll be included in the environment path. Just ls that bin folder and you'll find nothing more than the guile-next dependencies. No ls, no lesspipe, no dircolors On this, David's was assuming that I had read the manual already ;-) Now, as for the reason why ls, lesspipe and dircolors get called, David is right: the default .bashrc is full of stuff, it's a page long. So those "errors" are harmless. The resulting environment will be perfectly functional for Culturia to be explored ;-) Thanks again ! --089e0103e05c38a01d053e10d140 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Amirouche, David,

<= div class=3D"gmail_quote">2016-10-04 23:07 GMT+02:00 Amirouche Boubekki <amirouche@hypermove.net>:
On 2016-10-04 22:42, Catonano wrote:
In exploring Culturia, here

https://github.com/amirouche/Culturia/ [1]

I reach this line

guix environment --ad-hoc --pure guile-next


Both with and without --pure works on my side. I don't remember why I&#= 39;ve
put --pure in the README.

I use ubuntu 16.04.1, I have this in my ~/.zshrc

export PATH=3D"/home/amirouche/.guix-profile/bin":$PATH
export GUIX_LOCPATH=3D~/.guix-profile/lib/locale
export GUILE_LOAD_PATH=3D"/home/amirouche/.guix-profile/share/gui= le/site/2.2${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH"
export GUILE_LOAD_COMPILED_PATH=3D"/home/amirouche/.guix-profile/= share/guile/site/2.2${GUILE_LOAD_COMPILED_PATH:+:}$GUILE_LOAD_COMPILED_PATH"
export INFOPATH=3D"/home/amirouche/.guix-profile/share/info${INFO= PATH:+:}$INFOPATH"


Thanks to the both = of you

David's answer was a bit= terse althought straight to the point

Just to widen the discussion a bit, yes, in order to have basic command= s in a "pure" environment, even ls, they need to be explicitly in= cluded (either with the --ad-hoc clause or because they're dependencies= of some of the packages you're creating the env for)

In fact

guix= environment --pure --ad-hoc guile-next --search-paths

will show the "bin" that'll be included i= n the environment path. Just ls that bin folder and you'll find nothing= more than the guile-next dependencies. No ls, no lesspipe, no dircolors
On this, David's was assuming tha= t I had read the manual already ;-)
Now, as for the reason why ls, lesspipe a= nd dircolors get called, David is right: the default .bashrc is full of stu= ff, it's a page long.

So those = "errors" are harmless. The resulting environment will be perfectl= y functional for Culturia to be explored ;-)

Thanks again !
--089e0103e05c38a01d053e10d140--