From: David Thompson <dthompson2@worcester.edu>
To: guix-devel@gnu.org
Subject: [PATCH 0/2] Improve search path handling?
Date: Mon, 23 Feb 2015 21:11:33 -0500 [thread overview]
Message-ID: <87ioes9hyi.fsf@fsf.org> (raw)
While hacking on Ruby stuff, I noticed that executable files in Ruby
gems aren't installed in 'bin', but rather 'lib/ruby/gems/2.2.0/bin'.
In order to make these executables "just work", I decided to add a
search path specification for $PATH to the ruby package. That's when I
noticed an issue: 'guix package --search-paths' would have me clobber
the $PATH I had already configured to use my profile.
export PATH="/home/dave/.guix-profile/lib/ruby/gems/2.2.0/bin"
To solve this, two things need to happen: A default $PATH with 'bin' and
'sbin' needs to be included, and search path specifications that have
the same variable name need to be merged.
The merge is necessary to avoid a situation like this:
export PATH="/home/dave/.guix-profile/bin:/home/dave/.guix-profile/sbin"
export PATH="/home/dave/.guix-profile/lib/ruby/gems/2.2.0/bin"
I also tweaked 'guix environment' to use the base search paths, which it
was already doing, but via a hardcoded search path specification.
Or maybe this is all silly and I'm doing it wrong! You decide!
Thanks in advance for the patch review.
--
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate
next reply other threads:[~2015-02-24 2:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 2:11 David Thompson [this message]
2015-02-24 2:19 ` [PATCH 1/2] packages: Merge like search path specifications David Thompson
2015-02-27 16:03 ` Ludovic Courtès
2015-02-24 2:19 ` [PATCH 2/2] packages: Add %base-search-path-specifications David Thompson
2015-02-27 16:04 ` Ludovic Courtès
2015-02-25 3:04 ` [PATCH 0/2] Improve search path handling? David Thompson
2015-02-27 16:06 ` Ludovic Courtès
2015-02-28 17:31 ` David Thompson
2015-02-28 20:36 ` Andreas Enge
2015-03-02 6:17 ` Mark H Weaver
2015-03-02 9:27 ` Ludovic Courtès
2015-03-02 13:26 ` Dave Thompson
2015-03-02 14:27 ` 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
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=87ioes9hyi.fsf@fsf.org \
--to=dthompson2@worcester.edu \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).