From: "hsbt (Hiroshi SHIBATA) via ruby-core" Date: 2024-04-02T06:29:28+00:00 Subject: [ruby-core:117404] [Ruby master Feature#14217] Expose RUBY_PATCHLEVEL_STR or similar with patch level info for rc/preview as a constant Issue #14217 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Open to Closed This issues has been fixed at recent version of Bundler. https://github.com/rubygems/rubygems/pull/7016 ---------------------------------------- Feature #14217: Expose RUBY_PATCHLEVEL_STR or similar with patch level info for rc/preview as a constant https://bugs.ruby-lang.org/issues/14217#change-107566 * Author: shayonj (Shayon Mukherjee) * Status: Closed ---------------------------------------- ## Problem When ruby is in release candidate or preview, `RUBY_PATCHLEVEL` is `-1`. Without parsing `RUBY_DESCRIPTION`, its hard to tell using constant the right and absolute ruby version. ## Proposal Expose `RUBY_PATCHLEVEL_STR` as a constant, just like `RUBY_VERSION` or `RUBY_PATCHLEVEL`. So that, we can know the right ruby version, especially when its in preview or release candidate. This is also helpful when using gems that rely on `RUBY_PATCHLEVEL` and `RUBY_VERSION` to serve the right experience. Example: Bundler, which validates gem installation by making sure right ruby is installed. Currently, we cannot install gems using 2.5.0preview1. ~~~ Your Ruby version is 2.5.0, but your Gemfile specified 2.5.0preview1 ~~~ This can be handled in bundler through some different wokraround, but I think by exposing `RUBY_PATCHLEVEL_STR`, it will be helpful in building the appropriate solutions. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/