From: Michael Greenly Date: 2007-11-21T01:18:48+09:00 Subject: Re: RubyGems 0.9.5 Austin Ziegler wrote: > On 11/20/07, M. Edward (Ed) Borasky wrote: >> >> 1. Work with the packages as supplied by your distro. >> 2. *Don't* install the packages supplied by your distro -- use upstream >> source and put things in /usr/local. >> 3. Complain and whine to busy people who will blow you off. :) > > 4. Complain to your distro manager to be more sensible when it comes > to Ruby. Look closely at what Apple did for good suggestions. > > -austin I'm all ears if some one wants to fill me in on what Apple did... but... My issue is not with distribution packaging it's with the poor assumptions that RubyGems makes. It's not that I don't have a dozen options to work around this. It's that it will never 'just' work until RubyGems allows for these types of distribution requirements and there's absolutely no reason it can't. This latest update some how decided to install rubygems to /usr/local even though it was previously installed in /usr/lib and it moved it's gem cache from /var/lib/rubygems to /usr/lib/ruby/gems. Why? Now I realize the paticular oddities of this are not necessarily RubyGems problems. I was using the Ubuntu patched version, but I've looked at that patch and all it did was hardcode the GEM_HOME environment variable to be /var/lib/rubygems. Why would id decide to install into /usr/local? RubyGems has become a core part of Ruby. It needs to just work! As it is I still can't use it on production servers because I have no confidence it's not going to going to go mucking around in folders that don't belong to it. -- Posted via http://www.ruby-forum.com/.