From: Brian Andrews Date: 2008-08-09T13:54:21+09:00 Subject: Re: Ruby 1.8.7-p71 / 1.8.6-p286 released (Security Fix) Urabe Shyouhei wrote: > Brian Andrews wrote: >> How can a patch be considered "released" without the Windows binaries >> being made available? Is compiling the Ruby source code for Windows >> difficult? If so, what's the hangup? Binaries for all platforms should >> be available before any "patch" announcement is made. >> > > Ruby has never been officially released as binaries. It was always > released as source code. Waiting binaries for all platforms is simply > impossible; can you compile ruby binaries for HP-UX on Itanium? or for > AIX on POWER5? I think my "all platforms" comment was made in haste and is just confusing matters, so let me describe the issue that is directly affecting me... I'm a Ruby developer using 32-bit Windows. I download the Ruby binaries for Windows from: ftp://ftp.ruby-lang.org/pub/ruby/binaries/mswin32. I am assuming that these are the official binaries that the Ruby maintainers compile for 32-bit Windows. Is my assumption correct? After the announcement was made that several security vulnerabilities were found and have apparently been fixed in version 1.8.7 (on the main page of the Ruby website), I wanted to obtain the latest binaries for 32-bit Windows. I went to the ftp site for the Win32 binaries and could only find 1.8.7p22 (my current Ruby version). I expected to see a set of binaries for 1.8.7p71. Sorry if I'm coming across as brash. I'm not trying to be a jerk about this. I'm trying to understand how/when patched Ruby source code becomes a set of officially patched Win32 Ruby binaries available for download. I apologize for my ignorance and thanks for your patience and responses. -- Posted via http://www.ruby-forum.com/.