From: HiPhish <hiphish@posteo.de>
To: Luther Thompson <lutheroto@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Guix and $XDG_DATA_DIRS
Date: Fri, 12 Apr 2019 08:11:09 +0200 [thread overview]
Message-ID: <1622016.eWbK88MbK9@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <20190411190402.4852bbbc@gmail.com>
On Friday, 12 April 2019 01:04:02 CEST Luther Thompson wrote:
> Ok, so the profile and search-paths both have the same problem. I'll
> have to dig into the source code to see if I can find a root cause.
> Hopefully in the meantime, someone who knows about this stuff can come
> up with an answer.
>
> Luther
Now that I have looked into it, there are other variables that haven't been
defined as well that I had to define in my .profile file:
export GUIX_LOCPATH="$GUIX_PROFILE/lib/locale"
export INFOPATH="$HOME/.config/guix/current/share/info:$INFOPATH"
export CPATH="$HOME/.guix-profile/include/":$CPATH
export LD_LIBRARY_PATH="$HOME/.guix-profile/lib/":$LD_LIBRARY_PATH
export XDG_DATA_DIRS="$GUIX_PROFILE/share/":$XDG_DATA_DIRS
# SSL certificates (after installing 'nss-certs')
export SSL_CERT_DIR="$GUIX_PROFILE/etc/ssl/certs"
export SSL_CERT_FILE="$GUIX_PROFILE/etc/ssl/certs/ca-certificates.crt"
export GIT_SSL_CAINFO="$SSL_CERT_FILE"
I don't know if all of these should have been defined by Guix, but I have
listed them anyway. I could live with $XDG_DATA_DIRS not always being up to
date, but now I noticed that `guix environment --ad-hoc whatever` does not
make C libraries available for working on local projects because $CPATH AND
$LD_LIBRARY_PATH are not set.
next prev parent reply other threads:[~2019-04-12 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 17:06 Guix and $XDG_DATA_DIRS HiPhish
2019-04-11 17:58 ` Luther Thompson
2019-04-11 18:56 ` HiPhish
2019-04-11 23:04 ` Luther Thompson
2019-04-12 6:11 ` HiPhish [this message]
2019-04-12 9:11 ` Ricardo Wurmus
2019-04-12 12:20 ` HiPhish
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1622016.eWbK88MbK9@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=help-guix@gnu.org \
--cc=lutheroto@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.