On Wed, Sep 23, 2009 at 1:16 PM, DanS <dansteini...@gmail.com> wrote: > > but I still get the same error after installing bmabey-fakefs. I > notice that "gem list" command shows this as "fakefs" and not "bmabey- > fakefs" but I don't know if this naming difference matters, or what to > do about it if it does.
I'm glad you got the problem fixed by another route, but if it comes up again (or for the benefit of others): Most likely you hadn't added Github as a gem repository. The gem naming scheme you saw, "bmabey-fakefs," is how Github names all gems served out of its repository. It's not necessarily a _good_ way, and it's caused all sorts of headaches, but they stand by it due to their principle that no single Github repo is the "authoritative" one for a gem. To solve this problem permanently, run this on the command line at some point: > sudo gem sources --add http://gems.github.com If you just want to add Github to the repo list on a case-by-case basis, do this instead the next time you install a Github gem: > sudo gem install bmabey-fakefs --source http://gems.github.com -- Have Fun, Steve Eley (sfe...@gmail.com) ESCAPE POD - The Science Fiction Podcast Magazine http://www.escapepod.org _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
