On Fri, May 21, 2010 at 10:52 AM, Trans <transf...@gmail.com> wrote: > Actually, I think it is better that way. With RubyGems I am not even > sure why it bothers to divide gem install by ruby version, i.e. /usr/ > lib/ruby/gems/1.8/ vs. /usr/lib/ruby/gems/1.9/. That kind of division > made sense for setup.rb b/c installs would literally clobber each > other there, but that is no longer the case with gems. So why bother?
If there is a C extension in the gem, the Ruby extension API has some incompatibilities between 1.8.x and 1.9.x Also a gem which uses 1.9 Ruby syntax won't work on 1.8 either. -- Rick DeNatale Blog: http://talklikeaduck.denhaven2.com/ Github: http://github.com/rubyredrick Twitter: @RickDeNatale WWR: http://www.workingwithrails.com/person/9021-rick-denatale LinkedIn: http://www.linkedin.com/in/rickdenatale _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems Rubygems-developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
