[ruby-core:91588] [Ruby trunk Feature#15611] Shipping Bundler as a bundled gem, not a default gem

[mame@ruby-lang.org]

Issue #15611 has been updated by mame (Yusuke Endoh).


As far as I know, bundler is planned to be merged to rubygems.  If shipping bundler as a gem is ephemeral, it looks less significant to me whether bundler should be a bundled gem or a default one.

In fact, rubygems already includes some special code for bundler, e.g., [bundler_version_finder.rb](https://github.com/rubygems/rubygems/blob/master/lib/rubygems/bundler_version_finder.rb).  I think that it is going to be unreasonable to separate bundler as a gem.

Just my two cents,

----------------------------------------
Feature #15611: Shipping Bundler as a bundled gem, not a default gem
https://bugs.ruby-lang.org/issues/15611#change-76851

* 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/