From: Greg.mpls@... Date: 2019-05-01T16:22:14+00:00 Subject: [ruby-core:92517] [Ruby trunk Bug#15791] Clarify reason for RbConfig's ruby_version not reflecting "teeny" value 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/ Unsubscribe: