Issue #4666 has been updated by Lucas Nussbaum.


I this that this bug should be closed.

Either the ABI changed between 1.9.2 and 1.9.3, or it did not.

If it changed, then we are required to bump the SONAME, and that means upgrading the ruby compatibility level to 1.9.3.

If it did not change, there's no real interest (even for Debian) in providing co-installation of 1.9.2 and 1.9.3.

According to the discussion, it seems that the ABI should not be considered to have changed, even if some symbols were removed. Hence, let's just close this.
----------------------------------------
Feature #4666: set ruby compatibility version to 1.9.3 in trunk
http://redmine.ruby-lang.org/issues/4666

Author: Lucas Nussbaum
Status: Third Party's Issue
Priority: Low
Assignee: 
Category: 
Target version: 


Hi,

(I am one of the Debian maintainers for Ruby)

The trunk branch of Ruby still has a ruby compatibility version of 1.9.1, according to include/ruby/version.h.

The confusion between ruby version and ruby compatibility version caused a lot of questions in the ruby community. Even if 1.9.3 is still binary-compatible with 1.9.1, I think that it would be easier to change its ruby compat version to 1.9.3. This would:
- enable users to co-install (1.9.1 or 1.9.2) and 1.9.3. In debian, 1.9.3 could be provided as a separate ruby1.9.3 package.
- advertise the fact that there are API changes in 1.9.3 that could break apps

Thank you,


-- 
http://redmine.ruby-lang.org