[ruby-core:52400] Re: p385 breaks bakward compatibility

Dne nedト嬪e, 17. テコnora 2013 20:39:50 UTC+1 Andre Arko napsal(a):
>
> On Feb 17, 2013, at 1:23 AM, Vテュt Ondruch <[e-mail] <javascript:>> 
> wrote:
>
> Ruby releases should not violate common sense just to work around
> design flaws in ruby libraries, no matter how popular those libraries
> are.
>
>
> I agree even with this, that is why I am adding Bundler ML on CC. As a 
> interim solution, until Bundler gets fixed, I hope that #7869 will get 
> accepted.
>
>
> Bundler was created specifically so that this WOULD happen. I realize that 
> the situation is unpleasant for your particular use-case, but Bundler is 
> never going to compromise its core design principles in order to make the 
> case you are describing work. Sorry. :(
>
> That said, the issue you are describing should _never_ be a problem in 
> real life. Any time you update your ruby version, you absolutely need to 
> run `bundle install` again, to make sure that any compiled gems are 
> compiled correctly for the new ruby version that you have just installed. 
> If you run `bundle install` during your reproduction case, the problem goes 
> away completely:
>
> $ ruby -v
> ruby 1.9.3p374 (2013-01-15 revision 38858) [x86_64-darwin12.2.1]
>
> $ cat Gemfile
> source 'http://rubygems.org'
> gem 'rdoc'
>
> $ bundle exec rdoc --version
> rdoc 3.9.4
>
> # update ruby versions
>
> $ ruby -v
> ruby 1.9.3p385 (2013-02-06 revision 39114) [x86_64-darwin12.2.1]
>
> $ bundle install
> ERROR: Gem bundler is not installed, run `gem install bundler` first.
>
> $ gem install bundler
> Fetching: bundler-1.2.4.gem (100%)
> Successfully installed bundler-1.2.4
> 1 gem installed
>
> $ bundle install
> Fetching gem metadata from http://rubygems.org/.........
> Installing rdoc (3.9.4)
> Using bundler (1.2.4)
> Your bundle is complete! Use `bundle show [gemname]` to see where a 
> bundled gem is installed.
>
> $ bundle exec rdoc --version
> rdoc 3.9.4
>
>
First and foremost, it is not exactly my problem. I am fighting here for 
every Fedora, RHEL and CentOS user in the world and possibly also other 
Linux distributions. This issues makes impossible to use Ruby packaged in 
system! I am not speaking about some poor souls who tries to use gems 
distributed with the system and even collaborate with users of other 
platforms.

Bundler does this collaboration very hard and especially Gemfile.lock makes 
it almost impossible. The original idea of storing Gemfile.lock in you SCM 
works just in case you will neglect system packages and you work only with 
RubyGems itself. Of course RubyGems fails as soon as you try to install 
some database binding or XML parser, so neither usage of RubyGems is win.

Could you please reconsider your statement. Thank you.

Vテュt