From: Greg.mpls@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92517] [Ruby trunk Bug#15791] Clarify reason for RbConfig's ruby_version not reflecting "teeny" value
Date: Wed, 01 May 2019 16:22:14 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-77881.20190501162214.16660b7163680277@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15791.20190425154414@ruby-lang.org
Issue #15791 has been updated by MSP-Greg (Greg L).
I assume it was decided a long time ago. 1.9.3 has a value of 1.9.1.
Maybe a decision was made later that ABI versions would only change on minor releases?
----------------------------------------
Bug #15791: Clarify reason for RbConfig's ruby_version not reflecting "teeny" value
https://bugs.ruby-lang.org/issues/15791#change-77881
* Author: headius (Charles Nutter)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: all
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
I did not realize that MRI always reports `RbConfig::CONFIG['ruby_version']` without the "teeny" value. Instead, it makes it always 0:
```
$ rvm ruby-2.6.2 do ruby -v -e 'p RbConfig::CONFIG["ruby_version"]'
ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-darwin18]
"2.6.0"
```
This seems like a bug to me. It is a visible behavior because several package-management systems (RubyGems, Bundler, stuff in Ruby switchers like RVM) use this value, rather than RUBY_VERSION, to set up directory paths.
I believe it should reflect the full, accurate version, but I have not been able to find any discussion about why it does not do so.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-05-01 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15791.20190425154414@ruby-lang.org>
2019-04-25 15:44 ` [ruby-core:92408] [Ruby trunk Bug#15791] Clarify reason for RbConfig's ruby_version not reflecting "teeny" value headius
2019-04-25 18:44 ` [ruby-core:92411] " Greg.mpls
2019-04-27 19:49 ` [ruby-core:92445] " eregontp
2019-04-29 22:17 ` [ruby-core:92485] " headius
2019-05-01 16:22 ` Greg.mpls [this message]
2019-05-19 8:21 ` [ruby-core:92721] " v.ondruch
2019-06-27 20:50 ` [ruby-core:93389] " headius
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-77881.20190501162214.16660b7163680277@ruby-lang.org \
--to=ruby-core@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).