From: ludo@gnu.org (Ludovic Courtès)
To: Caleb Herbert <csh@bluehome.net>
Cc: help-guix@gnu.org
Subject: Re: Application Setup on Trisquel
Date: Thu, 26 Oct 2017 10:52:24 -0700 [thread overview]
Message-ID: <87po99g5k7.fsf@gnu.org> (raw)
In-Reply-To: <1508888666.10298@bluehome.net> (Caleb Herbert's message of "Tue, 24 Oct 2017 16:44:26 -0700 (PDT)")
"Caleb Herbert" <csh@bluehome.net> skribis:
>> > > The manual instructs users on foreign distros to export environment
>> > > variables. Doing this in the shell makes the changes temporary.
>> > > Where should these changes be made permanent? (It is bad
> practice to
>> > > put environment variables in .bashrc.)
>> >
>> > /etc/profile would be the right place.
>>
>> Is this correct?
>>
>> # echo 'export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale' >>/etc/p
>> rofile
>> # echo 'export SSL_CERT_DIR="$HOME/.guix-profile/etc/ssl/certs"' >>/
>> etc/profile
>> # echo 'export SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-c
>> ertificates.crt"' >>/etc/profile
>> # echo 'export GIT_SSL_CAINFO="$SSL_CERT_FILE"' >>/etc/profile
>> # echo 'export CURL_CA_BUNDLE="$HOME/.guix-profile/etc/ssl/certs/ca-
>> certificates.crt"' >>/etc/profile
>> # echo 'source $HOME/.guix-profile/etc/profile' >>/etc/profile
>
> I had to comment those lines in /etc/profile because Trisquel's
> display manager would return me to the login screen after entering my
> password.
Does ~/.xsession-errors contain hints as to why this happened?
> How do I make sure these environment variables are set?
For the variables themselves, /etc/profile is a good thing, as discussed
above.
I’d probably move “source $HOME/.guix-profile/etc/profile” to
~/.bash_profile, though.
But that’s really a shell question more than a Guix question, I think.
HTH!
Ludo’.
next prev parent reply other threads:[~2017-10-26 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:12 Application Setup on Trisquel Caleb Herbert
2017-10-24 21:16 ` Ludovic Courtès
2017-10-24 22:04 ` Caleb Herbert
2017-10-26 17:54 ` Ludovic Courtès
2017-10-27 1:02 ` Chris Marusich
2017-10-24 23:33 ` Caleb Herbert
2017-10-24 23:44 ` Caleb Herbert
2017-10-26 17:52 ` Ludovic Courtès [this message]
2017-10-26 20:05 ` Caleb Herbert
2017-10-25 0:36 ` Mikhail Kryshen
2017-10-26 17:53 ` Ludovic Courtès
2017-10-27 3:29 ` Caleb Herbert
2017-11-08 6:39 ` Caleb Herbert
2017-11-09 21:05 ` Chris Marusich
2017-11-10 21:29 ` Caleb Herbert
2017-11-12 14:55 ` Adonay Felipe Nogueira
2017-11-12 17:09 ` Adonay Felipe Nogueira
2017-11-12 13:02 ` Adonay Felipe Nogueira
2017-11-02 2:59 ` Mark H Weaver
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=87po99g5k7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=csh@bluehome.net \
--cc=help-guix@gnu.org \
/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).