That the built-in installation of Ruby on Mac OS X 10.5 (Leopard) is
structured in a peculiar way is a well-established fact. Nothing to do
with the system; it's the use of highly non-standard paths and
permissions for Ruby (including initial installation in a framework, in
a region to which the user has no write access, so e.g. outdated gems
can't be cleaned up - and what will happen when the user is ready to
update Ruby itself is completely unclear). But we've been up and down
this road before; nothing new to see here. m.
···
Luis Lavena <luislavena@gmail.com> wrote:
> Hrm, this is odd. I had a working RubyGems 1.1.0 on apple ruby when I
> released, but after removing it to restore the apple RubyGems 1.0.1, I
> am again stuck with 1.0.1 like you. Perhaps I did some other monkey-
> business that caused it to work correctly.
>
> I have an idea of what the problem is, but until I figure out exactly
> what the issue is, running:
>
> sudo update_rubygems
>
> installs RubyGems correctly.And then... someone says "Windows is broken"
Nevermind, just kidding
--
matt neuburg, phd = matt@tidbits.com, Matt Neuburg’s Home Page
Leopard - http://www.takecontrolbooks.com/leopard-customizing.html
AppleScript - http://www.amazon.com/gp/product/0596102119
Read TidBITS! It's free and smart. http://www.tidbits.com