diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2023-12-11 13:19:45 +0100 |
|---|---|---|
| committer | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2023-12-13 13:02:22 +0900 |
| commit | ac939d9ca3164a748c656ea7f33c356d7b91b0f9 (patch) | |
| tree | 867684d65fa0b00cfe3cb117fad59ebe4aaa67a6 /parser_node.h | |
| parent | 1a7aa5560f1a9967e320f71b7e8e8ee748151168 (diff) | |
[rubygems/rubygems] Improve default gem handling
If a gem is specified in the Gemfile (or resolved as a transitive
dependency), it's always resolved from remote/installed sources. Default
gems are only used as a fallback for gems not included in the bundle.
I believe this leads to more consistent behavior and more portable apps,
since all gems will be installed to the configured bundle path,
regardless of whether they are default gems or not.
https://github.com/rubygems/rubygems/commit/091b4fcf2b
Diffstat (limited to 'parser_node.h')
0 files changed, 0 insertions, 0 deletions