Hi, rake aborted! LoadError: cannot load such file -- coffee-script ... ... ... I eventually tracked this down to the gemspec generated by ruby-fakegem. When coffee-rails is installed manually with gem, the gemspec has this stuff; ==== if s.respond_to? :specification_version then s.specification_version = 4 if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then s.add_runtime_dependency(%q<coffee-script>.freeze, [">= 2.2.0"]) s.add_runtime_dependency(%q<railties>.freeze, ["< 5.1.x", ">= 4.0.0"]) else s.add_dependency(%q<coffee-script>.freeze, [">= 2.2.0"]) s.add_dependency(%q<railties>.freeze, ["< 5.1.x", ">= 4.0.0"]) end else s.add_dependency(%q<coffee-script>.freeze, [">= 2.2.0"]) s.add_dependency(%q<railties>.freeze, ["< 5.1.x", ">= 4.0.0"]) end ==== But the gemspec generated by ruby-fakegem has none of that. ruby-fakegem is generating a gemspec, instead of letting ruby build one because there is no "metadata", and there is no metadata because the ebuild fetches a tarball not a gem. As a quick fudge I commented out SRC_URI and removed the all_ruby_prepare(){} call (there is no Rakefile or test/test_helper.rb to run sed on) from dev-ruby/coffee-rails-4.1.1-r1.ebuild. The resulting package works nicely, the gemspec is correct.
This is now fixed in the -r2 revisions of coffee-rails 4.1 and 4.2. Thanks for reporting.
