From: Yukihiro Matsumoto <matz@...>
Date: 2010-07-13T03:47:34+09:00
Subject: [ruby-core:31218] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9

Hi,

In message "Re: [ruby-core:31215] [Bug #3140] gem activation has changed between 1.8 and 1.9"
    on Tue, 13 Jul 2010 02:51:04 +0900, Yehuda Katz <redmine@ruby-lang.org> writes:

|Bottom line: I cannot personally support a version of Ruby that can silently require a dependency that is explicitly disallowed by the parent. That possibility is ridiculous, and I'm amazed that, for months, it has been downplayed.
|
|If the problem is that ruby-core doesn't use RubyGems that much, and isn't willing to avoid breaking fundamental package manager properties, perhaps it's worth reconsidering including it in Ruby 1.9.

I am sorry that I haven't followed this issue.  As far as I
understand, this is caused by unfortunate timing.  Eric was busy at
the critical timing, most of us hesitated modifying it without Eric's
concent, and passing the maintainer role to Evan was late.

I think 1.9.2 should run Rails3.  If I understand what Yehuda told me
correctly, this issue could be a show stopper.  I know RC2 is so late
to add a change, but loosing Rails3 people is critical for 1.9.2
popularity.  I don't want to see 1.8.6 tragedy again.  It took us
years to overcome slight incompatibility with ActiveSupport.  Don't be
bureaucratic.

							matz.