Project

General

Profile

Actions
Copy link

Bug #11472

closed

Some default gems are not installed if GEM_HOME is set during Ruby installation

Added by vandrijevik (Vladimir Andrijevik) over 8 years ago. Updated about 5 years ago.

Status:
Rejected
Assignee:
hsbt (Hiroshi SHIBATA)
Target version:
-
ruby -v:
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]
Backport:
2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
[ruby-core:<unknown>]

Description

As of 2.2.3, the issue which I believe was fixed with this commit seems to be back: minitest, test-unit, and power_assert are not installed if GEM_HOME is set when building Ruby.

$ env | grep GEM
GEM_HOME=/Users/vladimir/ruby/default/gems
GEM_PATH=/Users/vladimir/ruby/default/gems

$ ruby-build 2.2.3 ~/ruby/2.2.3

$ ruby -v
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]

$ gem list

*** LOCAL GEMS ***

bigdecimal (1.2.6)
io-console (0.4.3)
json (1.8.1)
psych (2.0.8)
rake (10.4.2)
rdoc (4.2.0)

Doing the exact same installation, but making sure that GEM_HOME and GEM_PATH are not set, yields:

$ unset GEM_HOME
$ unset GEM_PATH
$ ruby-build 2.2.3 ~/ruby/2.2.3

$ ruby -v
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]

$ gem list

*** LOCAL GEMS ***

bigdecimal (1.2.6)
io-console (0.4.3)
json (1.8.1)
minitest (5.4.3)
power_assert (0.2.2)
psych (2.0.8)
rake (10.4.2)
rdoc (4.2.0)
test-unit (3.0.8)

I do not observe this behavior with Ruby 2.2.2, so I believe it is a regression introduced in 2.2.3. Thank you for your consideration, and please let me know if I did something wrong – this is my first time reporting an issue here.

Actions
Copy link

Also available in: Atom PDF

Like0
Like0Like0