From: nobu@... Date: 2016-01-08T13:07:33+00:00 Subject: [ruby-core:72775] [Ruby trunk - Bug #11956] RUBYOPT parses after rubygems loaded Issue #11956 has been updated by Nobuyoshi Nakada. Rubygems sets `Gem.path` at loading the first gem. Ruby 2.3 bundles `did_you_mean` and activates it by default. Why don't you set `GEM_HOME` and `GEM_PATH` directly instead of setting them in that file? ---------------------------------------- Bug #11956: RUBYOPT parses after rubygems loaded https://bugs.ruby-lang.org/issues/11956#change-56020 * Author: Am I Who * Status: Feedback * Priority: Normal * Assignee: * ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x64-mingw32] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- RUBYOPT=-rloader but loader.rb loads after rubygems.rb loaded I change GEM_HOME and GEM_PATH in loader.rb , but it doesn't affect Gem.path. The same loader.rb works at ruby 2.2.3(and before) and jruby. I uses both MRI ruby and jruby,so I uses RUBYOPT to changes GEM_HOME and GEM_PATH for different ruby engine -- https://bugs.ruby-lang.org/ Unsubscribe: