Created attachment 587394 [details] emerge --info When I use rubygems to install gems manually, it ignores gems installed by portage that can be used to satisfy dependencies and reinstalls them. An example of this behavior is the following. I wanted to install the sinatra-contrib gem, which isn't availlable in the portage tree. I issued the command sudo gem install sinatra-contrib expecting that only the sinatra-contrib gem would be installed, since I'd already installed all its dependencies (sinatra, mustermann, backports, tilt, rack-protection and multi_json) using portage. Instead, rubygems installed again all these gems (and their dependencies). I noticed this behavior after switching to the 17.1 profiles, but I can't say for sure that the switch was the cause. I'm sure that in the past this behavior didn't occur.
Which version of dev-ruby/rubygems do you have installed? Does it help to move back to rubygems-3.0.3?
I'm using rubygems 3.0.6, but downgrading to 3.0.3 doesn't solve the issue.
Any news about this? On my system this is still happening. Today I tried to manually install the roo gem using gem install roo Both as root and as common user, rubygems wanted to install its racc and nokogiri dependencies which I'd already installed using portage. After installing roo with the --ignore-dependencies option, it worked correctly, which means that at runtime gems installed by portage are found by ruby/rubygems. The problem only regards the installation time.
