From: Austin Ziegler Date: 2007-11-21T05:14:36+09:00 Subject: Re: RubyGems 0.9.5 On 11/20/07, Michael Greenly wrote: > Austin Ziegler wrote: > > 4. Complain to your distro manager to be more sensible when it comes > > to Ruby. Look closely at what Apple did for good suggestions. > I'm all ears if some one wants to fill me in on what Apple did... Look to posts by Laurent Sansonetti on this list or the rubygems developer list. > 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. There's also absolutely no reason it should. There are plenty of options if you're having to update a system location, as Eric Hodel has pointed out in the past. > 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? Right. But you installed an *upstream* package (gem update --system) over a *downstream* package. RubyGems is absolutely *correct* to assume that I want RubyGems itself to be in the same location as Ruby. If I want something different (which, frankly, *I* don't) then I have options available through environment variables. Again, see recent posts by Eric Hodel for sanctioned options, or Laurent's summary of Leopard changes to see how you're advised to upgrade RubyGems on Leopard. It's not "gem update --system", but it's not significantly harder (I think it's SOME_ENV_VAR=other-location gem update --system). > RubyGems has become a core part of Ruby. It needs to just work! Fact: it does. > 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. I don't know why you can't. I'd have no problem using Ruby and RubyGems on a production server at all. I'd just never use an Ubuntu package for Ruby or RubyGems. Ever. (Why? The upstream maintainers at Debian Don't Get Ruby. While the situation is better than it has been, it's still a freaking nightmare.) -austin -- Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/ * austin@halostatue.ca * http://www.halostatue.ca/feed/ * austin@zieglers.ca