Project

General

Profile

Actions

Bug #12983

closed

compatibility_version and current_version on Darwin are reversed

Added by knu (Akinori MUSHA) over 7 years ago. Updated over 7 years ago.

Status:
Closed
Assignee:
-
Target version:
-
[ruby-core:78387]

Description

The compatibility_version should have an API version and the current_version should have a program version of Ruby, but they have been reversed and the binary compatibility has never worked.

For example, the ruby 2.3.3 program/dylib shows the following versions:

% otool -L /opt/local/bin/ruby2.3
/opt/local/bin/ruby2.3:
        /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1259.0.0)
        /opt/local/lib/libruby.2.3.0.dylib (compatibility version 2.3.3, current version 2.3.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1226.10.1)
        /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

The compatibility version is updated for every teeny release, and all extensions need to be updated accordingly, which is not an expected or welcome situation.

https://github.com/ruby/ruby/pull/1495

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0