From: eregontp@... Date: 2019-04-27T19:49:10+00:00 Subject: [ruby-core:92445] [Ruby trunk Bug#15791] Clarify reason for RbConfig's ruby_version not reflecting "teeny" value Issue #15791 has been updated by Eregon (Benoit Daloze). Indeed, AFAIK it's the ABI version. MSP-Greg (Greg L) wrote: > If the version with 'teeny' was used, one would be recompiling extension gems everytime a 'teeny' release was done? Which IMHO is a safer thing to do, but I suppose some people disagree and it depends on the point of view :) FWIW, I created https://github.com/postmodern/chruby/pull/410 so `chruby` would have a set of gems per installed Ruby version, even if `RUBY_VERSION` or `RbConfig::CONFIG["ruby_version"]` doesn't change for alternative Ruby implementations between two releases. ---------------------------------------- Bug #15791: Clarify reason for RbConfig's ruby_version not reflecting "teeny" value https://bugs.ruby-lang.org/issues/15791#change-77796 * 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: