dev-ruby/ruby-postgres-0.7.1.20051221 doesn't work with rails-1.1.6 but dev-ruby/ruby-postgres-0.7.1 work ==============ruby-postgres-0.7.1.20051221============================= localhost 0.1 # irb irb(main):001:0> require 'postgres' LoadError: no such file to load -- postgres from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from (irb):1 ==============dev-ruby/ruby-postgres-0.7.1============================== localhost 0.1 # irb irb(main):001:0> require 'postgres' => true
I can confirm this.
$ ruby /usr/lib/ruby/gems/1.8/gems/ruby-postgres-0.7.1.2005.12.21/tests/tc_postgres.rb /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- postgres (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib/ruby/gems/1.8/gems/ruby-postgres-0.7.1.2005.12.21/tests/tc_postgres.rb:1
This is not a bug in this package - unfortunately a really stupid patch got applied to rubygems upstream for 0.9.0 which totally screws up extensions that are built in the installation process. The shortest option to fix this at the moment would be to change the following lines within /usr/lib/ruby/site_ruby/1.8/rubygems/installer.rb (or your local equivalent) Approximately lines 588 and 605 will look like ['', 'install', 'clean'].each do |target| change both to read [''].each do |target| This will undo the patch nonsense and get this ebuild working again. Hopefully someone upstream will smarten up and remove this garbage from rubygems. The 0.7.1 version isn't affected because it's a source build as opposed to rubygems based
Will patch rubygems-0.9.0-r1 with the same patch applied upstream.
And finally, fixed.
