Prev: Pingecho, causing SocketError.
Next: Iteration through File.file? misses entries for which File.file?(entry) == true -- FIXED
From: Marc Zampetti on 2 Aug 2010 15:22
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?
--
Posted via http://www.ruby-forum.com/.

From: Luis Lavena on 2 Aug 2010 15:57
On Aug 2, 4:22 pm, Marc Zampetti <zampet...(a)aim.com> 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.

--
Luis Lavena
 | 
Pages: 1
Prev: Pingecho, causing SocketError.
Next: Iteration through File.file? misses entries for which File.file?(entry) == true -- FIXED