Latest Windows installer is backdated

ruby-talk
1

I also found that the latest Ruby Windows installer’s (1.8.1-12) version of
win32ole.so doesn’t work properly for me. After rebuilding .exe’s using
exerb that once worked on a previous version (1.8.0-10), the .exe’s fail to
run properly. I’m not good enough to trace the real problem. My solution
was to replace the new win32ole.so (distributed with 1.8.1-12) with the
previous version I had (distributed with 1.8.0-10). Now, .exe’s that are
generated with exerb work properly.
Craig
PS - Should this go under a different Subject line?

···

-----Original Message-----
From: Bret Pettichord [mailto:bret@pettichord.com]
Sent: Thursday, April 22, 2004 1:25 PM
To: ruby-talk@ruby-lang.org
Subject: Latest Windows installer is backdated

I found some interesting/anomolous reporting with ruby -v.

Ruby windows installer 1.8.1-11 gives:

ruby 1.8.1 (2004-01-27) [i386-mswin32]

Ruby windows installer 1.8.1-12 (which is newer) gives:

ruby 1.8.1 (2003-12-25) [i386-mswin32]

This seems backwards. Why?

Bret Pettichord, Software Tester
Consultant - www.pettichord.com
Author - www.testinglessons.com
Blogger - www.io.com/~wazmo/blog

Homebrew Automation Seminar
April 30, Austin, Texas
www.pettichord.com/training.html
2

Moran, Craig M wrote:

I also found that the latest Ruby Windows installer’s (1.8.1-12)
version of
win32ole.so doesn’t work properly for me. After rebuilding .exe’s using
exerb that once worked on a previous version (1.8.0-10), the
.exe’s fail to
run properly. I’m not good enough to trace the real problem. My solution
was to replace the new win32ole.so (distributed with 1.8.1-12) with the
previous version I had (distributed with 1.8.0-10). Now, .exe’s that are
generated with exerb work properly.

Does it work with the version of winole32 that shipped with version 1.8.1-11
of the installer?

Curt