Issue #6124 has been updated by nahi (Hiroshi Nakamura).

Subject changed from What is the purpose of "fake" gems in Ruby to remove the "spec-only gems" in Ruby 1.9.3 (was What is the purpose of "fake" gems in Ruby)
Status changed from Closed to Open

Vit proposed either of these;
(1) remove the "spec-only gems" in Ruby 1.9.3
(2) make "default gems" from the "spec-only" gems right now for Ruby 1.9.3

Since (2) should wait for #5481 and 2.0 so (1) is the only option right now I think.

I'm positive for (1). Thoughts?
----------------------------------------
Bug #6124: remove the "spec-only gems" in Ruby 1.9.3 (was What is the purpose of "fake" gems in Ruby)
https://bugs.ruby-lang.org/issues/6124#change-27629

Author: vo.x (Vit Ondruch)
Status: Open
Priority: Normal
Assignee: nahi (Hiroshi Nakamura)
Category: 
Target version: 
ruby -v: ruby 1.9.3p0 (2011-10-30) [x86_64-linux]


As I tried to point out in #6123, the "fake" gems which are distributed with Ruby breaks user's expectations. The following example should fail:

$ ruby --disable-gems -e "puts require('bigdecimal')"
true

However, it is not failing. Could you please enlighten me what is the purpose of fake gem then? Even if you install updated BigDecimal from rubygems.org, the bundled version will won unless you use "gem 'bidgecimal'" somewhere in the code. This makes no sense.

Don't take me wrong, I am big fan of gemified stdlib #5481, however this is not the way how it should be done.


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