1.9.2 RC2 Uses 1.9.1 for various directories

Using 1.9.2 RC2 and building from source, I am seeing the install use
1.9.1 as the directory that various sub dirs are using, like vendorlib,
gems, etc. In previous releases, this was usually 1.9. Is the change to
a 3-level version for these dirs intended, and if so, why is 1.9.1 used
for a 1.9.2 release?

On Aug 2, 4:22 pm, Marc Z. [email protected] wrote:

Using 1.9.2 RC2 and building from source, I am seeing the install use
1.9.1 as the directory that various sub dirs are using, like vendorlib,
gems, etc. In previous releases, this was usually 1.9. Is the change to
a 3-level version for these dirs intended, and if so, why is 1.9.1 used
for a 1.9.2 release?

1.9.1 stand for Ruby API compatibility, and is used for Ruby C
extension to determine any API change between versions.

This means that Ruby 1.9.2 is API compatible with 1.9.1

Is possible that in the future Ruby 1.9.3 introduce API breakage and
gain its own version of API (1.9.3)

Look for “Ruby 1.9 versioning scheme and packaging” in Ruby-Core
mailing list.

This means that Ruby 1.9.2 is API compatible with 1.9.1

The only incompatibility I’ve found is ruby-debug gem. Perhaps it
should be moved into core?
-r

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs