Issue #15611 has been updated by hsbt (Hiroshi SHIBATA).

Status changed from Assigned to Rejected

>Is there a particular reason to have Bundler as a default gem?

Already @mame said. Bundler will merge into RubyGems in the feature. In fact, after RubyGems 2.7+ integrated the part of dependency resolver of Bundler. 
Therefore We should test Bundler and RubyGems every commits of CRuby. If We shipped Bundler as bundled gems, We couldn't test its integrated parts.

PS. The RubyGems and Bundler team are going to discuss its details at before/after Dev MTG in RubyKaig 2019.



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

* Author: Eregon (Benoit Daloze)
* Status: Rejected
* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>