On Wed, Oct 17, 2018 at 2:13 PM Clément Lassieur <clem...@lassieur.org> wrote:
>
> Hi Laura,
>
> Laura Lazzati <laura.lazzati...@gmail.com> writes:
>
> > You were right. I took a look at my .bashrc file, and I had an:
> > export PATH="/home/laura/.guix-profile/bin${PATH:+:}$PATH"
> > I ran $guix pull, did the PATH export in my CLI, then checked the output of
> > $which guix, that was the same that was mentioned by you,
> > commented that previous line in .bashrc,
> > added export PATH="/home/laura/.config/guix/current/bin${PATH:+:}$PATH"
> > and ran again the command to check the available R packages, made a
> > diff with the previous one, and now at least r-bae appears.
>
> You should export environment variables such as PATH in
> ‘~/.bash_profile’ instead of ‘~/.bashrc’. :-)
>
> Quoting the documentation[1]:
>
> Users sometimes wrongfully augment environment variables such as
> ‘PATH’ in their ‘~/.bashrc’ file. As a consequence, when ‘guix
> environment’ launches it, Bash may read ‘~/.bashrc’, thereby
> introducing “impurities” in these environment variables. It is an
> error to define such environment variables in ‘.bashrc’; instead,
> they should be defined in ‘.bash_profile’, which is sourced only by
> log-in shells. See ‘Bash Startup Files[2]’, for details on Bash
> start-up files.
Thanks! I am reading that part now, specially [2].
I have deleted the env variables from .bashrc and have just set them
in .profile, since my distro is Ubuntu, and I am reading that Ubuntu
does not use .bash_profile. Everything seems to be working fine. Thank
you again :)
> Cheers,
> Clément
>
> [1]:
> https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-environment.html#FOOT15
> [2]:
> https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html#Bash-Startup-Files
