From: hsbt@...
Date: 2019-03-13T00:27:51+00:00
Subject: [ruby-core:91805] [Ruby trunk Bug#11472] Some default gems are not installed if GEM_HOME is set during Ruby installation

Issue #11472 has been updated by hsbt (Hiroshi SHIBATA).

Status changed from Assigned to Rejected

I couldn't reproduce it.

```
~ > mkdir .gem_home
~ > set -x GEM_HOME ~/.gem_home
~ > rbenv install 2.5.0-dev
ruby-build: use openssl from homebrew
Cloning https://github.com/ruby/ruby.git...
Installing ruby-2.5.0-dev...
ruby-build: use readline from homebrew
Installed ruby-2.5.0-dev to /Users/hsbt/.rbenv/versions/2.5.0-dev

~ > rbenv shell 2.5.0-dev
~ > gem list

*** LOCAL GEMS ***

bigdecimal (default: 1.3.4)
cmath (default: 1.0.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.0)
etc (default: 1.0.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
minitest (5.10.3)
net-telnet (0.1.1)
openssl (default: 2.1.2)
power_assert (1.1.1)
psych (default: 3.0.2)
rake (12.3.0)
rdoc (default: 6.0.1)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.7)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
```

rbenv could install the bundled gems like `test-unit`, `minitest` and `xmlrpc` and install the all of default gems.

----------------------------------------
Bug #11472: Some default gems are not installed if GEM_HOME is set during Ruby installation
https://bugs.ruby-lang.org/issues/11472#change-77079

* Author: vandrijevik (Vladimir Andrijevik)
* Status: Rejected
* Priority: Normal
* 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
----------------------------------------
As of 2.2.3, the issue which I believe was fixed with [this commit](https://github.com/ruby/ruby/commit/ec171c45975b525bbe5d63b92f1521622aa05394) 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.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>