hmans/rbfu

GEM_PATH doesn't include 1.8/1.9 dir

ku1ik opened this issue · 5 comments

ku1ik commented

I have just tried to use ruby versions I had installed for rbenv with rbfu and I found slight difference in GEM_PATH between rbenv and rbfu.

For 1.9.2-p320 when I enable it via rbfu I get

GEM_PATH=/home/kill/.rbfu/rubies/1.9.2-p320/lib/ruby/gems

When I enable the same ruby installation via rbenv I get

GEM_PATH=/home/kill/.rbfu/rubies/1.9.2-p320/lib/ruby/gems/1.9.1

I checked on RVM and I also observed that it adds 1.9.1 to the end. The same happens for ruby 1.8 versions (1.8 gets added on rvm/rbenv).

I wonder why rvm/rbenv are using this longer path and why rbfu isn't.

I wanted to reuse ruby installations I already had and have them used by both rbenv and rbfu (I'm evaluating rbfu so it's nice to not have to compile the same rubies again). But right now I can't share rubies because gem installation paths are different.

ku1ik commented

I'm not saying (yet) rbfu is doing it wrong, I'm just curious where the difference comes from and what's the recommended (by upstream) GEM_PATH setting.

mpapis commented

RVM sets custom paths to separate gems form ruby:

/home/mpapis/.rvm/gems/ruby-1.9.3-p194-nx:/home/mpapis/.rvm/gems/ruby-1.9.3-p194-nx@global

as for your question you can compare version of rubygems - maybe that's the difference.

hmans commented

Thanks for bringing this up. I will investigate. I'll be working on gem locations a bit before 1.0 anyway.

mpapis commented

can this be closed?