From: "mame (Yusuke Endoh)" Date: 2021-12-25T07:45:31+00:00 Subject: [ruby-core:106819] [Ruby master Feature#17468] Deprecate RUBY_DEVEL Issue #17468 has been updated by mame (Yusuke Endoh). When packaging a new tarball, we faced this issue again. Building a tarball produces so many warnings: ``` ./vm_debug.h:34:5: warning: "RUBY_DEVEL" is not defined, evaluates to 0 [-Wundef] 34 | #if RUBY_DEVEL | ^~~~~~~~~~ ./vm_debug.h:100:5: warning: "USE_RUBY_DEBUG_LOG" is not defined, evaluates to 0 [-Wundef] 100 | #if USE_RUBY_DEBUG_LOG | ^~~~~~~~~~~~~~~~~~ In file included from ./vm.c:40: ./vm_sync.h:7:5: warning: "USE_RUBY_DEBUG_LOG" is not defined, evaluates to 0 [-Wundef] 7 | #if USE_RUBY_DEBUG_LOG | ^~~~~~~~~~~~~~~~~~ ``` ---------------------------------------- Feature #17468: Deprecate RUBY_DEVEL https://bugs.ruby-lang.org/issues/17468#change-95630 * Author: naruse (Yui NARUSE) * Status: Open * Priority: Normal * Target version: 3.1 ---------------------------------------- Some configuration of Ruby use RUBY_DEVEL, which depends PATCH_LEVEL. But depending PATCH_LEVEL causes issues which will become revealed on the final release. Though we release some previews and RCs, they don't contributes the quality around RUBY_DEVEL. Therefore to ensure CI tests the quality of the final release, we need to deprecate RUBY_DEVEL. -- https://bugs.ruby-lang.org/ Unsubscribe: