dev-ruby/twitter-0.1.1 crash with error: /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- active_support (LoadError) from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/lib/twitter.rb:1 from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/lib/twitter.rb:1:in `each' from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/lib/twitter.rb:1 from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `gem_original_require' from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require' from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/bin/twitter:32 from /usr/bin/twitter:16:in `load' from /usr/bin/twitter:16 if dev-ruby/activesupport it's not installed. Reproducible: Always Steps to Reproduce: 1. unmask dev-ruby/twitter-0.1.1 2. install dev-ruby/twitter-0.1.1 in a system without dev-ruby/activesupport 3. run 'twitter' Actual Results: It fails with the following trace: /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- active_support (LoadError) from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/lib/twitter.rb:1 from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/lib/twitter.rb:1:in `each' from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/lib/twitter.rb:1 from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `gem_original_require' from /usr/lib64/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require' from /usr/lib64/ruby/gems/1.8/gems/twitter-0.1.1/bin/twitter:32 from /usr/bin/twitter:16:in `load' from /usr/bin/twitter:16 Expected Results: It should output: Usage: twitter <command> [options] Available Commands: - post - timeline - friends - friend - followers - follower - featured - important
This looks like it's an upstream issue, because the gem we use to install doesn't specify a dependency on activesupport. It seems to be fixed in newer upstream releases (0.2.1).
I've added twitter 0.2.1 to CVS in order to fix this.