added in bug #162463. in ~ since may 1 2007. thanks.
We really should be having a stable rubygems 0.9.x in the tree, but since we've had a number of problems with rubygems 0.9 I'm still a bit hesitant to stable it now. My proposal would be to wait two more weeks and then request rubygems 0.9.4 to be made stable. Ruby herd: any thoughts or preferences on this?
I'd like to request the stabilization of dev-ruby/rubygems-0.9.4. We've had some mixed success with rubygems-0.9.x versions, but this version seems to be stable and not suffering from upgrade issues like previous versions, and there have been no new bug reports in the 6 weeks that it has been in CVS.
ppc64 stable
ppc stable.
Stable for HPPA.
>>> Compiling source in /var/tmp/portage/dev-ruby/rubygems-0.9.4/work/rubygems-0.9.4 ... /usr/bin/ruby: no such file to load -- auto_gem (LoadError) !!! ERROR: dev-ruby/rubygems-0.9.4 failed. Call stack: ebuild.sh, line 1621: Called dyn_compile ebuild.sh, line 973: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile rubygems-0.9.4.ebuild, line 38: Called die !!! setup.rb config failed !!! If you need support, post the topmost build error, and the call stack if relevant. on ia64, ideas? x86 stable
Flameeyes helped me with my problem, ia64 stable
sparc stable.
amd64 stable