From: David Masover <ninja@...>
Date: 2008-06-09T16:58:48+09:00
Subject: Re: Gems error concerning yaml

On Monday 09 June 2008 02:03:39 Michael Litchard wrote:
> Then why would gems break on a yaml install when I tried to install rails?

I don't know. Why would you try to install yaml directly? I don't see it as a 
requirement for Rails anymore -- try "gem install rails" and see what 
happens.

> # gem18 install yaml --include-dependencies
...
> ERROR:  could not find yaml locally or in a repository

That pretty clearly tells you that "yaml" does not exist as a library, and 
that you should look for it elsewhere.

> It seems to me, if yaml is part of the  base install, then gems should not
> try to install it.

There isn't any way, right now, for a gem to be part of the base install. 
There isn't even a one-to-one mapping between gems (as in gem install foo) 
and libraries (as in require 'foo').

I'm not convinced that's an ideal architecture, but that's how it is.

So are you suggesting that there should be a list of keywords for which 
Rubygems will say "I think you mean something that's now part of core"?