diff options
| author | Jeremy Evans <code@jeremyevans.net> | 2025-11-02 21:47:42 -0800 |
|---|---|---|
| committer | git <svn-admin@ruby-lang.org> | 2025-11-04 00:17:49 +0000 |
| commit | bac6a25ad3b6ed02ece11a2790cec3a2e6f8c8c9 (patch) | |
| tree | 347e11e40fe6d2c4bc3d4ea094dd45fcb14093e3 /include/ruby/debug.h | |
| parent | 4001e81a8eb04ac1b7653b05762bcdcb364760e1 (diff) | |
[ruby/rubygems] Remove open-ended and prerelease dependency warnings when building gems
In general, rubygems should provide mechanism and not policy.
Pessimistic versioning is not universally better, and in many
cases, it can cause more problems than it solves. Rubygems should
not be warning against open-ended versioning when building gems.
The majority of the default gems with dependencies do not use
pessimistic versioning, which indicates that Ruby itself
recognizes that open-ended versioning is generally better.
In some cases, depending on a prerelease gem is the only choice
other than not releasing a gem. If you are building an extension
gem for a feature in a prerelease version of another gem, then
depending on the prerelease version is the only way to ensure
a compatible dependency is installed.
https://github.com/ruby/rubygems/commit/beba8dd065
Diffstat (limited to 'include/ruby/debug.h')
0 files changed, 0 insertions, 0 deletions
