https://rubygems.org/gems/rubygems-update I am hitting gems that declare they need >= 1.4.
Sort-of in the works. Our patches need rather extensive forward-porting.
I've added rubygems 1.8.5 to the tree, but it is still masked since it needs more testing and it currently lacks support for jruby and ruby19. I haven't tested ruby19 yet. jruby has incompatible code in its own ruby_engine defaults.
The latest version of rubygems is 1.8.10: http://production.cf.rubygems.org/rubygems/rubygems-1.8.10.tgz It's a separate issue really, but I'd love it if I could emerge this and keep my system purely ruby 1.9.x.
I've just added a virtual/rubygems to the tree. This will allow us to give up on having one unbundled rubygems version for all ruby targets since each target is making its own changes to rubygems and has specific version requirements. It is my expectation that only ruby 1.8 and ruby-enterprise will use the unbundled version in the future. At that point we can also unmask newer versions and bump to the latest rubygems.
rubygems 1.8.10 is now in the tree. Still masked until compatibility with jruby is resolved.
And now unmasked since jruby is fixed to work with this version.