![]() I chose this fix because it's reasonably simple and I think it shouldn't affect how other parts of bundler function.Įver since upgrading to Ruby 2.6, I've experienced the following crash # Why did you choose this fix out of the possible options? My fix is to also include the set of default gems, unless they are already included in the gemfile dependencies. # What is your fix for the problem, implemented in this PR? My diagnosis was that when bundler replaces the set of gems known to rubygems, it restricts the world to what's in the Gemfile (or resolved from it), and that doesn't include default gems. # What was your diagnosis of the problem? In my opinion, this completely defeats the purpose of default gems, and makes bundler degrade the user experience instead of making it better. The problem was that since `irb` and others were moved to default gems, users cannot directly use them in a bundler context, unless they add it to their gemfiles. ![]() # What was the end-user problem that led to this PR? 6963: Allow to `bundle exec` default gems r=deivid-rodriguez a=deivid-rodriguez
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |