diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2024-11-18 13:41:41 +0100 |
|---|---|---|
| committer | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2024-11-26 15:11:05 +0900 |
| commit | 6386d49f9e2443db8ecb59b9be7ce5b2be9f1cd3 (patch) | |
| tree | 838edd7315bac4e29b764ae50c2fad6908eabf95 /test/ruby | |
| parent | 7c9346033197128a40c76dffa1745757132ff623 (diff) | |
[rubygems/rubygems] Fix development dependencies considered unnecessarily sometimes
When used with `LazySpecification` objects, `SpecSet#for` was
incorrectly considering development dependencies. This did not cause any
issues because all usages of this method with `LazySpecification`'s are
not strict, meaning the pass `check = false` and ignore incomplete
specifications. But it was still doing more work than necessary because
development dependencies were still added to the `deps` array for
processing and then ignored because of not being found in the spec set.
Same when converging path specifications and replacing their dependencies.
https://github.com/rubygems/rubygems/commit/6afca8a95f
Diffstat (limited to 'test/ruby')
0 files changed, 0 insertions, 0 deletions
