Created attachment 396158 [details] emerge-info.txt This was originally going to be about a collision with dev-ruby/power_assert, but it looks like that's fixed now (sort of). The last time I synced, both dev-ruby/power_assert and dev-lang/ruby:2.2 were installing the power_assert gem under /usr/local. Now it looks like dev-ruby/power_assert is fixed: $ equery f dev-ruby/power_assert ... /usr/lib64/ruby/gems/2.2.0/gems/power_assert-0.2.2 /usr/lib64/ruby/gems/2.2.0/gems/power_assert-0.2.2/lib /usr/lib64/ruby/gems/2.2.0/gems/power_assert-0.2.2/lib/power_assert ... But ruby:2.2 is still installing it under /usr/local! $ equery f ruby:2.2 | grep power_assert ... /usr/local/lib64/ruby/gems/2.2.0/cache/power_assert-0.2.2.gem /usr/local/lib64/ruby/gems/2.2.0/gems/power_assert-0.2.2 /usr/local/lib64/ruby/gems/2.2.0/gems/power_assert-0.2.2/.gitignore ... The interesting part of the build log: installing bundle gems: /usr/local/lib64/ruby/gems/2.2.0 (build_info, cache, doc, extensions, gems, specifications) test-unit-3.0.8.gem power_assert-0.2.2.gem minitest-5.4.3.gem The package manager isn't allowed to touch /usr/local, but if you fix that, there's going to be a collision again. I don't think I'm doing anything tricky. $ ACCEPT_KEYWORDS="~amd64" USE=-doc emerge -pv1 ruby:2.2 [ebuild R ] dev-lang/ruby-2.2.0:2.2 USE="ipv6 ncurses rdoc readline ssl -berkdb -debug -doc -examples -gdbm -jemalloc -rubytests -socks5 -xemacs" 0 KiB
Created attachment 396160 [details] ruby-2.2.0-build.log
Did you check config.log for hints ?
I'm aware of this issue. It only happens on a fresh install which is why I did not notice this initially. In any case these gems should be unbundled when installing.
(In reply to Hans de Graaff from comment #3) > I'm aware of this issue. It only happens on a fresh install which is why I > did not notice this initially. In any case these gems should be unbundled > when installing. Actually the gems always get installed, so the files either end up in /usr/local on a fresh install, or in /usr on an existing install, where they will then cause file collisions. ruby-2.2.0-r1 properly unbundles these gems and makes sure they are installed with PDEPEND.