From: mikadoZero <mikadozero@yandex.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: 14.1 Building from Git
Date: Wed, 20 Mar 2019 17:20:02 -0400 [thread overview]
Message-ID: <cucpnqljla5.fsf@yandex.com> (raw)
In-Reply-To: <871s32n8xo.fsf@elephly.net>
Ricardo Wurmus writes:
> mikadoZero <mikadozero@yandex.com> writes:
>
>> I did copy the suggested exports that were output when I ran `guix
>> package --manifest=manifest.scm` into .zprofile and they were:
>
> I suggest to not do this and to add this snippet instead:
>
> export GUIX_PROFILE="$HOME/.guix-profile"
> source $GUIX_PROFILE/etc/profile
>
It is now in my .bash_profile.
>> I commented out all of the above export of environment variables in
>> .zprofile and ran `guix environment --pure guix` then ran `printenv` but
>> that has not changed the order. /root/.guix-profile directories are
>> still first.
>
> “guix environment --pure” spawns a sub-shell. You need to ensure that
> for sub-shells the variables are not set — this is currently not the
> case as evidenced by printenv. I don’t know about what files zsh reads
> under what conditions, so I cannot recommend a way around this.
>
> You could also try to use Bash instead.
Thank you
I have been able to switch my non root users shell from zsh to bash.
Now with a user that has a bash shell I am able to continue on using the
contributing section of the manual as a guide and can do: bootstrap,
configure, `./pre-inst-env guix lint package-name` and `./pre-inst-env
guix build --rounds=4 package-name`.
next prev parent reply other threads:[~2019-03-20 21:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 20:50 14.1 Building from Git mikadoZero
2019-03-18 10:08 ` Giovanni Biscuolo
2019-03-18 19:16 ` mikadoZero
2019-03-18 12:37 ` Ricardo Wurmus
2019-03-18 19:05 ` mikadoZero
2019-03-18 19:28 ` Leo Famulari
2019-03-19 15:39 ` mikadoZero
2019-03-18 19:54 ` Ricardo Wurmus
2019-03-19 15:34 ` mikadoZero
2019-03-19 16:08 ` Ricardo Wurmus
2019-03-20 21:20 ` mikadoZero [this message]
2019-03-19 19:17 ` Tobias Geerinckx-Rice
2019-03-20 21:25 ` mikadoZero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cucpnqljla5.fsf@yandex.com \
--to=mikadozero@yandex.com \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).