From: deivid.rodriguez@... Date: 2019-02-19T09:25:32+00:00 Subject: [ruby-core:91589] [Ruby trunk Feature#15611] Shipping Bundler as a bundled gem, not a default gem Issue #15611 has been updated by deivid (David Rodr��guez). Yes, I was going to comment exactly along the same lines mame presents. Also, moving bundler to a default gem would still keep the same problem in https://bugs.ruby-lang.org/issues/15610, but only for the rubygems code. Although to be honest, having duplicated versions of the rubygems code in rubylibdir and site_ruby has not yet led to real world issues that I know of. But still, moving both to site_ruby feels cleaner and safer to me. ---------------------------------------- Feature #15611: Shipping Bundler as a bundled gem, not a default gem https://bugs.ruby-lang.org/issues/15611#change-76852 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Target version: ---------------------------------------- I think this would simplify many things, and would allow to update or remove the shipped Bundler easily on Ruby 2.6. Is there a particular reason to have Bundler as a default gem? Also, given how Bundler magically switches which version is used based on the Gemfile, it seems better to have each Bundler version in its own directory, rather thank risking to load multiple Bundler versions or parts of it from lib/, site_ruby/ and the bundler gem directory. -- https://bugs.ruby-lang.org/ Unsubscribe: