Created attachment 189073 [details] update to 2.7.3 I initially suggested this change on ruby mailing-list: https://lists.freebsd.org/pipermail/freebsd-ruby/2017-November/007778.html Since then I have been using RubyGems 2.7.1, 2.7.2, and now 2.7.3 (attached patch). Most issues I listed in my original mail were fixed upstream: https://github.com/rubygems/rubygems/commit/4053fda6d552f6ce13e56d922aeda3876d23f1fe https://github.com/rubygems/rubygems/commit/4619f13a33642b132ebcc4e82772d89b4bcff0d3 https://github.com/rubygems/rubygems/commit/f5872d0e4d3c6553107086c9f73d81cd2b851e81 The last one is about RubyGems installing bundler gem (sysutils/rubygem-bundler, http://bundler.io/) as "bundled gem". This same concept exists in ruby, but the FreeBSD port has a patch to prevent installing those gems, since they are provided as separate ports. The issue here is that the code to install this gem does not handle --destdir option correctly, I attempted to fix it, but it requires dedicated code for a specific OS under which I cannot test easily: https://github.com/rubygems/rubygems/pull/2106 Anyway I'm not sure it's worth the trouble fixing it, because I assume we do not want to install it for the FreeBSD port. So this update adds a new patch to avoid installing "bundled gems": devel/ruby-gems/files/patch-lib_rubygems_commands_setup__command.rb I tested it successfully with a few gems, but far from all. Should I try some kind of "exp-run" locally for all ports depending on devel/ruby-gems?
*** This bug has been marked as a duplicate of bug 224677 ***