From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: guix environment
Date: Tue, 16 Jun 2015 07:52:47 +0200 [thread overview]
Message-ID: <20150616055247.GA23591@thebird.nl> (raw)
In-Reply-To: <CAJ=RwfZNB4aUimgTguRvQUQj5eoaaOG0=jVRzgd0nKoovREPCA@mail.gmail.com>
On Mon, Jun 15, 2015 at 03:22:55PM -0400, Thompson, David wrote:
> On Mon, Jun 15, 2015 at 3:10 PM, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> > On Mon, Jun 15, 2015 at 09:10:15AM -0400, Thompson, David wrote:
> >> On Mon, Jun 15, 2015 at 2:55 AM, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> >> >
> >> > Would it be OK to add some RUBY paths?
> >>
> >> What additional Ruby search paths are needed? We already have $GEM_PATH.
> >
> > $GEM_HOME
>
> This one doesn't make sense because it specifies where gems are to be
> installed. Store items are immutable, so one cannot install gems into
> them.
We still provide the gem tool ;). If we set this value to something
sensible (relative to $HOME) people can still use gems. The current
default setting is not good because it does not provide isolation.
I realise this may not be a guix concern, but for guix adoption it is
good to think about these things.
> > $GEM_SPEC_CACHE
>
> Is this a real search path or can it only point to a single cache
> directory? If the latter, it cannot be a native search path in a
> package recipe.
Same reasoning. We want isolation between different Ruby
installations. That is what I do in that script - pick up the HASH and
create a path relative to $HOME.
If this is what every normal user needs to do, why can't we have guix
help out? Ultimately it is part of the Ruby environment we work in -
therefore it is the resposibility of the Ruby package. It does away
with needing RVM :)
We can ignore this point, but it means every user will have to work
around it. What is the point of that?
Pj.
next prev parent reply other threads:[~2015-06-16 5:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 6:55 guix environment Pjotr Prins
2015-06-15 7:14 ` Ricardo Wurmus
2015-06-15 13:10 ` Thompson, David
2015-06-15 19:10 ` Pjotr Prins
2015-06-15 19:22 ` Thompson, David
2015-06-16 5:52 ` Pjotr Prins [this message]
2015-06-16 7:59 ` Ludovic Courtès
2015-06-16 10:04 ` Pjotr Prins
2015-06-16 11:23 ` Ludovic Courtès
2015-06-16 14:39 ` Pjotr Prins
2015-06-15 13:27 ` Claes Wallin (韋嘉誠)
2015-06-15 20:09 ` Ludovic Courtès
2015-06-16 5:06 ` Claes Wallin (韋嘉誠)
-- strict thread matches above, loose matches on Subject: below --
2019-06-01 16:53 H.Nasajpour<PantherX>
2019-06-01 18:42 ` Christopher Baines
2015-01-20 17:21 Federico Beffa
2015-01-20 21:43 ` Ludovic Courtès
2015-01-20 21:56 ` David Thompson
2015-01-29 23:00 ` David Thompson
2015-02-03 20:29 ` Ludovic Courtès
2015-02-03 21:15 ` David Thompson
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=20150616055247.GA23591@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=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 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.