Bug 322537 – ruby-1.8.7_p249-r2 and rubygems missing (?) "dependency" check

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description mjbjr 2010-06-03 05:51:30 UTC]

I just installed ruby-1.8.7_p249-r2 and got this message:

>>> Installing (1 of 1) dev-lang/ruby-1.8.7_p249-r2
!!! Warning: Could not set gem symlink
It appears you do not have RubyGems installed for this profile.
(For Ruby 1.8 you have to emerge >=dev-ruby/rubygems-1.2.0-r1)

(I missed that rubygems version requirement(?) )

yet, emerging rubygems installs rubygems-1.3.7 without a "check" or "warning"
or a problem, afaik.

Does ruby-1.8 (still) require rubygems-1.2?

Also, the phrasing of that warning message seems to imply that rubygems should be installed *before* ruby.  That seems unlikely.

---------
>>> Emerging (1 of 1) dev-ruby/rubygems-1.3.7-r1
 * rubygems-1.3.7.tgz RMD160 SHA1 SHA256 size ;-) ...                                                                    [ ok ]
 * checking ebuild checksums ;-) ...                                                                                     [ ok ]
 * checking auxfile checksums ;-) ...                                                                                    [ ok ]
 * checking miscfile checksums ;-) ...                                                                                   [ ok ]
 * CPV:  dev-ruby/rubygems-1.3.7-r1
 * REPO: gentoo
 * USE:  amd64 elibc_glibc kernel_linux multilib ruby_targets_ruby18 userland_GNU

...

>>> Install rubygems-1.3.7-r1 into /var/tmp/portage/dev-ruby/rubygems-1.3.7-r1/image/ category dev-ruby
 * Running install phase for ruby18 ...
RubyGems 1.3.7 installed

���=== 1.3.7 / 2010-05-13





Reproducible: Always

[Comment 1 Alex Legler (RETIRED) 2010-06-03 11:50:25 UTC]

RubyGems is not a hard dependency. If you want it, you need to install it after emerging Ruby.

I've rephrased the message in eselect-ruby a little.

[Comment 2 Alex Legler (RETIRED) 2010-06-03 14:40:55 UTC]

Fix is in eselect-ruby-20100603.