From: Eric Hodel Date: 2008-06-11T03:16:28+09:00 Subject: Re: Gems error concerning yaml On Jun 9, 2008, at 09:57 AM, Michael Litchard wrote: > On Mon, Jun 9, 2008 at 12:58 AM, David Masover > wrote: > >> 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"? >> >> > no no. but when I did a gems install ruby, it choked on one of the > dependencies. It was yaml. There is no yaml gem, so it couldn't fail to be installed as a dependency, as no gem lists it as a dependency. Can you paste the exact text of this failure? Maybe the actual error message you got can be reworded in order to prevent confusion. > I ended up using netbsd's pkgsrc to install rails. It's working now. > But I > don't understand why gems would think I needed to download yaml, and > then > choke when it couldn't find it. Other package managers I have used > don't do > this. Since there's no yaml gem, of course RubyGems will "choke" it. Other package managers "choke" on things that don't exist: MacPorts: $ port install nosuchport Error: Port nosuchport not found FreeBSD's pkg_add: $ pkg_add -r nosuchpackage Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/Latest/nosuchpackage.tbz : File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/Latest/nosuchpackage.tbz' by URL FreeBSD's portupgrade: $ portupgrade -N nosuchport ** No such installed package or port: nosuchport RubyGems: $ gem install nosuchgem ERROR: could not find gem nosuchgem locally or in a repository