[#97536] [Ruby master Bug#16694] JIT vs hardened GCC with PCH — v.ondruch@...
Issue #16694 has been reported by vo.x (Vit Ondruch).
11 messages
2020/03/18
[ruby-core:97356] [Ruby master Misc#16671] BASERUBY version policy
From:
naruse@...
Date:
2020-03-04 08:24:41 UTC
List:
ruby-core #97356
Issue #16671 has been updated by naruse (Yui NARUSE). Through the discussion around CI, I reached a conclusion "Runtime environment and development environment are different". Though CentOS and macOS bundles very old ruby, but it's no problem because they are just runtime environment. If people want to develop Ruby master on those environment, they can install latest stable ruby with tarball. Therefore BASERUBY can be a reasonable newer stable version. It means newer than Ruby installed by default on for example CentOS. ---------------------------------------- Misc #16671: BASERUBY version policy https://bugs.ruby-lang.org/issues/16671#change-84483 * Author: ko1 (Koichi Sasada) * Status: Open * Priority: Normal ---------------------------------------- Ruby 2.7 (MRI) requires Ruby 2.2 or later (== BASERUBY) to build from repository. Tarball does not need any installed Ruby. To build latest Ruby from repository, you need to build Ruby 2.2 and later from a tarball. Can we make the BASERUBY version update policy? # Background To use `ISeq#to_a` (specific format) Ruby 2.2 or later is needed from Ruby 2.7. The oldest version used by RubyCI machines was Ruby 2.2, so I determined update. I needed to file a ticket about this version bump, sorry. --- related: https://bugs.ruby-lang.org/issues/16668 -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>