From: Troy Sankey <sankeytms@gmail.com>
To: guix-devel@gnu.org
Subject: support for non-list search paths
Date: Mon, 06 Mar 2017 11:08:29 -0500 [thread overview]
Message-ID: <148881650998.9901.885151305016110036@what> (raw)
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
The file "~/.guix-profile/etc/profile" treats all search paths as
colon-separated lists. Some variables are not supposed to be lists, but
treating them as such could confuse programs which read them.
GIT_EXEC_PATH is one that has caused me trouble, so I'll be using it as
an example below.
The relevant line from "~/.guix-profile/etc/profile":
% grep GIT_EXEC_PATH ~/.guix-profile/etc/profile
export GIT_EXEC_PATH="${GUIX_PROFILE:-/gnu/store/9wwv7rl8n6ydcpa0h22nd38amwssfrbh-profile}/libexec/git-core${GIT_EXEC_PATH:+:}$GIT_EXEC_PATH"
Here's what my GIT_EXEC_PATH looks like from a terminal emulator:
% echo $GIT_EXEC_PATH
/home/sankey/.guix-profile/libexec/git-core:/home/sankey/.guix-profile/libexec/git-core
Here's the error from git:
% git rebase
/home/sankey/.guix-profile/libexec/git-core/git-sh-setup: line 46: /home/sankey/.guix-profile/libexec/git-core:/home/sankey/.guix-profile/libexec/git-core/git-sh-i18n: No such file or directory
Since my shell rcfile is sourced twice, GIT_EXEC_PATH becomes a
colon-separated list. Double-sourcing the shell rcfile may not be the
only way to surface this issue. If my rcfile simply set GIT_EXEC_PATH
before sourcing "~/.guix-profile/etc/profile", then I would still end up
with a corrupt GIT_EXEC_PATH.
My workaround involves using `guix package --search-paths=exact`, but
this cost me some time debugging which I'd like to save the next person.
I am not sure what the solution should be. Maybe just a clarification
in documentation? What about an argument for search-path-specification
to force the variable to always be "exact"?
Troy
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
-----BEGIN PGP SIGNATURE-----
iQIzBAABCAAdFiEE0zLJ6STd4Cp+CgbIgs677ofYV8IFAli9iW8ACgkQgs677ofY
V8K9fxAAqFIJMp5/NYbPpg34jnknFzqEiPyJDILV0blNn9h+Fy3JEBHYh29kQCCo
Wgw/gAclSFt8ZOCvM7lqATwYF5vsEPfnXDHBij8eVwIPalx2Y6+crtRALMlt1aAa
HAvMJ0JixkLAVap+LeGj1I5Me/Kxgcco1B7/tnviSqrQqnpr6DWoKfkT/XIPtQU0
dquFF5CMKlMzBSyGTYpN4RvMF/OVEJ09nVLJdg3GwYmDN7Hrknf4yupM/c6Dp18I
KrAiW7ofMNXQMDR80lCuJPdd1F36d6HhkRtxSfEaxFNJxrjafldT5o4L+Xfg9xx6
G5MBFqX1N8Kj5YoDptszT1lE69t2lhll4+eKUogLbXsMrBkcaDV1LTk2Hif83QwD
hOT4yr0qoLSVyidUA9PNPrJi/gJqVwiHE9dW/7WnAblI9xNNdItfu1fOdv5KURGM
gbjDj5Ew2yZ32j/7cDLBedKTuh0Nf2PcFd703HIl8V2isZEuAEh7yewd2u6xxf1a
1bD/dMcdG6b8R6SUHQNCzP3gjC1VsJQKh/N/iBkDOUddPJya044UhmGUEDrX6k5l
Y3Bi603N9Tr6cjw/eYqKAVA7s3o4gegiVg7t1CqXDM+7hBJZd8hxkQ05v4bIm2Dh
j5yudWtRzwbUZbjhP0wb+iUkSc36bXkQx3hkoKT/h0TP+44NYfM=
=h4xm
-----END PGP SIGNATURE-----
next reply other threads:[~2017-03-06 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 16:08 Troy Sankey [this message]
2017-03-06 21:22 ` support for non-list search paths Ludovic Courtès
2017-03-07 0:43 ` Troy Sankey
2017-03-08 8:46 ` Ludovic Courtès
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=148881650998.9901.885151305016110036@what \
--to=sankeytms@gmail.com \
--cc=guix-devel@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.
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.