From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:117404] [Ruby master Feature#14217] Expose RUBY_PATCHLEVEL_STR or similar with patch level info for rc/preview as a constant
Date: Tue, 02 Apr 2024 06:29:28 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-107566.20240402062928.13521@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-14217.20171222004602.13521@ruby-lang.org
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/
parent reply other threads:[~2024-04-02 6:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <redmine.issue-14217.20171222004602.13521@ruby-lang.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-107566.20240402062928.13521@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).