From roger.pack at leadmediapartners.com  Tue Jun  3 15:08:22 2008
From: roger.pack at leadmediapartners.com (Roger Pack)
Date: Tue, 3 Jun 2008 13:08:22 -0600
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
Message-ID: <966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>

in other related news...
now that github can host some gems
http://gems.github.com/
maybe we should just post 'mingw' friendly gems there of the things
that we like.
like mongrel, mysql, ruby-debug, eventmachine, etc.?
Then we would only have to have one person build it once and [phew]
the rest of us could use it :)

From roger.pack at leadmediapartners.com  Tue Jun  3 15:10:26 2008
From: roger.pack at leadmediapartners.com (Roger Pack)
Date: Tue, 3 Jun 2008 13:10:26 -0600
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
Message-ID: <966599840806031210u4a384b3w312f6d563fd03f0f@mail.gmail.com>

as a note, here are mingw instructions for rmagick
http://rubyforge.org/forum/message.php?msg_id=55720


On Tue, Jun 3, 2008 at 1:08 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> in other related news...
> now that github can host some gems
> http://gems.github.com/
> maybe we should just post 'mingw' friendly gems there of the things
> that we like.
> like mongrel, mysql, ruby-debug, eventmachine, etc.?
> Then we would only have to have one person build it once and [phew]
> the rest of us could use it :)
>

From rogerpack2005 at gmail.com  Tue Jun  3 18:44:46 2008
From: rogerpack2005 at gmail.com (Roger Pack)
Date: Tue, 3 Jun 2008 16:44:46 -0600
Subject: [Rubyinstaller-devel] mingw openssl test failure
Message-ID: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>

Downloaded a fresh install of mingw today and got this:

C:\downloads\latest\installer3>rake check
(in C:/downloads/latest/installer3)
"C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i
-c "make check"
test succeeded
./miniruby.exe  ../ruby_1_8/runruby.rb --extout=.ext --
"../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test"
--runner=console

Loaded suite .
Started
..................................................................................................................................
..................................................................................................................................
...................../ruby_1_8/test/openssl/test_hmac.rb:30: [BUG]
Segmentation fault
ruby 1.8.6 (2008-03-03) [i386-mingw32]


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.


Anybody seen that before?
Thanks!
-R

From luislavena at gmail.com  Tue Jun  3 18:54:15 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Tue, 3 Jun 2008 19:54:15 -0300
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
Message-ID: <71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>

On Tue, Jun 3, 2008 at 7:44 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
> Downloaded a fresh install of mingw today and got this:
>
> C:\downloads\latest\installer3>rake check
> (in C:/downloads/latest/installer3)
> "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i
> -c "make check"
> test succeeded
> ./miniruby.exe  ../ruby_1_8/runruby.rb --extout=.ext --
> "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test"
> --runner=console
>

Are you grabbing the sources from code.mmediasys.com or the github tarballs?

The most up-to-date are the github tarballs, since didn't had tiem to
update the sync script for both svn repository and the zip package.

In the dump site:

http://dump.mmediasys.com/installer3/

You can see the text file (.txt) that contains the only errors during
"rake check", of course excluding the test/readline/test_readline.rb
file since it stall the whole procedure.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From roger.pack at leadmediapartners.com  Tue Jun  3 18:57:07 2008
From: roger.pack at leadmediapartners.com (Roger Pack)
Date: Tue, 3 Jun 2008 16:57:07 -0600
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
	<71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
Message-ID: <966599840806031557t2e8ccc2bm505eb805ca5dd200@mail.gmail.com>

http://code.mmediasys.com/installer3/latest.zip

On Tue, Jun 3, 2008 at 4:54 PM, Luis Lavena <luislavena at gmail.com> wrote:
> On Tue, Jun 3, 2008 at 7:44 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
>> Downloaded a fresh install of mingw today and got this:
>>
>> C:\downloads\latest\installer3>rake check
>> (in C:/downloads/latest/installer3)
>> "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i
>> -c "make check"
>> test succeeded
>> ./miniruby.exe  ../ruby_1_8/runruby.rb --extout=.ext --
>> "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test"
>> --runner=console
>>
>
> Are you grabbing the sources from code.mmediasys.com or the github tarballs?
>
> The most up-to-date are the github tarballs, since didn't had tiem to
> update the sync script for both svn repository and the zip package.
>
> In the dump site:
>
> http://dump.mmediasys.com/installer3/
>
> You can see the text file (.txt) that contains the only errors during
> "rake check", of course excluding the test/readline/test_readline.rb
> file since it stall the whole procedure.
>
> --
> Luis Lavena
> AREA 17
> -
> Human beings, who are almost unique in having the ability to learn from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>

From roger.pack at leadmediapartners.com  Tue Jun  3 20:11:39 2008
From: roger.pack at leadmediapartners.com (Roger Pack)
Date: Tue, 3 Jun 2008 18:11:39 -0600
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <966599840806031633v3d642201oaa438f24562587bf@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<966599840806031633v3d642201oaa438f24562587bf@mail.gmail.com>
Message-ID: <966599840806031711u780f97bcw8447032267944256@mail.gmail.com>

I'm slightly confused as to how to use gems with the latest git mingw installer.

I'd think that I should be able to run

c:\dev\latest\rubyinstaller\sandbox>  rubygems_mingw\bin\gem.bat list

and it would show 'no gems listed'
It defaults instead to using the installed msvc ruby.exe
Glancing at it I assume we have to install to c:\Ruby now?

Here's my attempt to run it with the right ruby.exe

c:\dev\latest\rubyinstaller\sandbox>ruby_mingw\bin\ruby.exe
rubygems_mingw\bin\gem
rubygems_mingw/bin/gem:8:in `require': no such file to load --
rubygems (LoadError)
        from rubygems_mingw/bin/gem:8


As a side note, you may also you may want to consider a few more
explicit directory names, since they were somewhat confusing to me
this [and every] time.
ruby_1_8 -> ruby_1_8_src
rubygems -> rubygems_src

To avoid confusion.
I could do it if you want.

Thanks!
-R


On Tue, Jun 3, 2008 at 5:33 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> thanks.
> I took the liberty of doing some readline research.  Probably all
> useless, but...
> http://betterlogic.com/roger/?p=312
> there they are.  I might try them out sometime.  If I
>
> Note that I get the same hmac segfault using a clone of the github repo.
> -R
>
>
> On Tue, Jun 3, 2008 at 5:07 PM, Luis Lavena <luislavena at gmail.com> wrote:
>> On Tue, Jun 3, 2008 at 8:00 PM, Roger Pack
>> <roger.pack at leadmediapartners.com> wrote:
>>> could you drop me a link to the discussion?
>>
>> http://rubyforge.org/pipermail/rubyinstaller-devel/2008-April/000288.html
>>
>> And before I run out of battery, grab the tarball from github and use
>> that instead:
>>
>> http://github.com/luislavena/rubyinstaller/
>>
>> --
>> Luis Lavena
>> AREA 17
>> -
>> Human beings, who are almost unique in having the ability to learn from
>> the experience of others, are also remarkable for their apparent
>> disinclination to do so.
>> Douglas Adams
>>
>

From gthiesfeld at gmail.com  Wed Jun  4 00:47:10 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Tue, 3 Jun 2008 23:47:10 -0500
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <966599840806031711u780f97bcw8447032267944256@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<966599840806031633v3d642201oaa438f24562587bf@mail.gmail.com>
	<966599840806031711u780f97bcw8447032267944256@mail.gmail.com>
Message-ID: <e9ece6840806032147i54478ee5x4ab1f00897ba7d88@mail.gmail.com>

On Tue, Jun 3, 2008 at 7:11 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> I'm slightly confused as to how to use gems with the latest git mingw installer.
>
> I'd think that I should be able to run
>
> c:\dev\latest\rubyinstaller\sandbox>  rubygems_mingw\bin\gem.bat list
>
> and it would show 'no gems listed'
> It defaults instead to using the installed msvc ruby.exe
> Glancing at it I assume we have to install to c:\Ruby now?
>
> Here's my attempt to run it with the right ruby.exe
>
> c:\dev\latest\rubyinstaller\sandbox>ruby_mingw\bin\ruby.exe
> rubygems_mingw\bin\gem
> rubygems_mingw/bin/gem:8:in `require': no such file to load --
> rubygems (LoadError)
>        from rubygems_mingw/bin/gem:8
>

>From what I understand, the rubygems install was moved out of the ruby
install to facilitate the MSI creation, as ruby and rubygems will be
listed as seperate features in the installer (or at least the Wix
files refer to them as features).  During the MSI installation
process, they would both be installed to the same location.  To run
it, you could copy the contents of rubygems_mingw into ruby_mingw.  Of
course, that's kind of hacky.  Another option would be to flesh out
the Wix automation, so that you can build the MSI package and install
it via Rake ;-)

> As a side note, you may also you may want to consider a few more
> explicit directory names, since they were somewhat confusing to me
> this [and every] time.
> ruby_1_8 -> ruby_1_8_src
> rubygems -> rubygems_src
>
> To avoid confusion.
> I could do it if you want.

This was confusing to me too at first, but I've just been staring at
it a lot and the confusion went away ;-).  I certainly wouldn't be
opposed to a change.

> Thanks!
> -R
>

Hope that helps,

Gordon

From gthiesfeld at gmail.com  Wed Jun  4 00:53:56 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Tue, 3 Jun 2008 23:53:56 -0500
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <e9ece6840806032147i54478ee5x4ab1f00897ba7d88@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<966599840806031633v3d642201oaa438f24562587bf@mail.gmail.com>
	<966599840806031711u780f97bcw8447032267944256@mail.gmail.com>
	<e9ece6840806032147i54478ee5x4ab1f00897ba7d88@mail.gmail.com>
Message-ID: <e9ece6840806032153w20544c29g69273bbceba0928d@mail.gmail.com>

On Tue, Jun 3, 2008 at 11:47 PM, Gordon Thiesfeld <gthiesfeld at gmail.com> wrote:
> On Tue, Jun 3, 2008 at 7:11 PM, Roger Pack
> <roger.pack at leadmediapartners.com> wrote:
>> I'm slightly confused as to how to use gems with the latest git mingw installer.
>>
>> I'd think that I should be able to run
>>
>> c:\dev\latest\rubyinstaller\sandbox>  rubygems_mingw\bin\gem.bat list

I also meant to say that up until the recent split of ruby_mingw and
rubygems_mingw folders, I was testing by just changing my path env
variable.  I have a batch script that removes the installed ruby and
adds the sandbox ruby to path.  This only effects the current command
session, so no harm done.  And, you can just type:

>gem list

and it will use the sandbox ruby.

From luislavena at gmail.com  Wed Jun  4 03:44:34 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 4 Jun 2008 04:44:34 -0300
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <966599840806031711u780f97bcw8447032267944256@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<966599840806031633v3d642201oaa438f24562587bf@mail.gmail.com>
	<966599840806031711u780f97bcw8447032267944256@mail.gmail.com>
Message-ID: <71166b3b0806040044v3f7d43e0qfdfcaa3846f16ef9@mail.gmail.com>

On Tue, Jun 3, 2008 at 9:11 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> I'm slightly confused as to how to use gems with the latest git mingw installer.
>
> I'd think that I should be able to run
>
> c:\dev\latest\rubyinstaller\sandbox>  rubygems_mingw\bin\gem.bat list
>

For the ruby interpreter to work you need 'bin' folder in the PATH

There was a change in rubygems between 1.0 and 1.1 to allow
installation of gems outside the default gem home.

> and it would show 'no gems listed'
> It defaults instead to using the installed msvc ruby.exe
> Glancing at it I assume we have to install to c:\Ruby now?
>
> Here's my attempt to run it with the right ruby.exe
>
> c:\dev\latest\rubyinstaller\sandbox>ruby_mingw\bin\ruby.exe
> rubygems_mingw\bin\gem
> rubygems_mingw/bin/gem:8:in `require': no such file to load --
> rubygems (LoadError)
>        from rubygems_mingw/bin/gem:8
>
>
> As a side note, you may also you may want to consider a few more
> explicit directory names, since they were somewhat confusing to me
> this [and every] time.
> ruby_1_8 -> ruby_1_8_src
> rubygems -> rubygems_src
>

That is doable.

> To avoid confusion.
> I could do it if you want.

Please, feel free to fork rubyinstaller repository at github and test
it by yourself, then send me a pull request. I don't have enough time
(or battery) right now to do it.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From rogerpack2005 at gmail.com  Wed Jun  4 10:12:02 2008
From: rogerpack2005 at gmail.com (Roger Pack)
Date: Wed, 4 Jun 2008 08:12:02 -0600
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
	<71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
Message-ID: <E581A151-26E9-427F-A8E2-EC6EA1C0F7E9@gmail.com>

if you get time, could I get a copy of the build that results in 'only  
a few' errors
as you mentioned, and outputs its errors here

http://dump.mmediasys.com/installer3/
?

I wonder if it differs from mine somehow.
Did it have openssl installed and run those tests, too?
-R

On Jun 3, 2008, at 4:54 PM, Luis Lavena wrote:

> On Tue, Jun 3, 2008 at 7:44 PM, Roger Pack <rogerpack2005 at gmail.com>  
> wrote:
>> Downloaded a fresh install of mingw today and got this:
>>
>> C:\downloads\latest\installer3>rake check
>> (in C:/downloads/latest/installer3)
>> "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i
>> -c "make check"
>> test succeeded
>> ./miniruby.exe  ../ruby_1_8/runruby.rb --extout=.ext --
>> "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test"
>> --runner=console
>>
>
> Are you grabbing the sources from code.mmediasys.com or the github  
> tarballs?
>
> The most up-to-date are the github tarballs, since didn't had tiem to
> update the sync script for both svn repository and the zip package.
>
> In the dump site:
>
> http://dump.mmediasys.com/installer3/
>
> You can see the text file (.txt) that contains the only errors during
> "rake check", of course excluding the test/readline/test_readline.rb
> file since it stall the whole procedure.
>
> -- 
> Luis Lavena
> AREA 17
> -
> Human beings, who are almost unique in having the ability to learn  
> from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel


From luislavena at gmail.com  Wed Jun  4 11:47:38 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Wed, 4 Jun 2008 12:47:38 -0300
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <E581A151-26E9-427F-A8E2-EC6EA1C0F7E9@gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
	<71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
	<E581A151-26E9-427F-A8E2-EC6EA1C0F7E9@gmail.com>
Message-ID: <71166b3b0806040847i62726fa6ue8a3be832479355d@mail.gmail.com>

On Wed, Jun 4, 2008 at 11:12 AM, Roger Pack <rogerpack2005 at gmail.com> wrote:
> if you get time, could I get a copy of the build that results in 'only a
> few' errors
> as you mentioned, and outputs its errors here
>
> http://dump.mmediasys.com/installer3/
> ?
>

http://dump.mmediasys.com/installer3/ruby-1.8.6-p114-i386-mingw32-2.txt

What I needed to do was merge both ruby_mingw and rubygems_mingw since
was splitted for MSI setup creation.

> I wonder if it differs from mine somehow.
> Did it have openssl installed and run those tests, too?

I used the the same version of ruby I'm distributing to test, and
actually the tests run on top of this version and not the installed
one.
(dunno if that's clear, let me rephrase: tests uses the sandbox ruby
version, not the one you used to build the sandbox).

If test are failing that means something hacked your PATH because the
test add the sandboxed ruby _before_ anything else, so if there is an
openssl dll, will find it there first.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From gthiesfeld at gmail.com  Wed Jun  4 13:10:11 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Wed, 4 Jun 2008 12:10:11 -0500
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
Message-ID: <e9ece6840806041010n30512510kf921b0829b005d86@mail.gmail.com>

On Tue, Jun 3, 2008 at 5:44 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
> Downloaded a fresh install of mingw today and got this:
>
> C:\downloads\latest\installer3>rake check
> (in C:/downloads/latest/installer3)
> "C:/downloads/latest/installer3/sandbox/msys/bin/bash.exe" --login -i
> -c "make check"
> test succeeded
> ./miniruby.exe  ../ruby_1_8/runruby.rb --extout=.ext --
> "../ruby_1_8/test/runner.rb" --basedir="../ruby_1_8/test"
> --runner=console
>
> Loaded suite .
> Started
> ..................................................................................................................................
> ..................................................................................................................................
> ...................../ruby_1_8/test/openssl/test_hmac.rb:30: [BUG]
> Segmentation fault
> ruby 1.8.6 (2008-03-03) [i386-mingw32]
>
>
> This application has requested the Runtime to terminate it in an unusual way.
> Please contact the application's support team for more information.
>
>
> Anybody seen that before?

Actually, I just remembered I have seen that before ;-).  I was having
the same problem a few months ago, which was caused by having another
version of libeay32.dll and libssl32.dll in my system path.  Luis
helped me with it on this thread:

http://rubyforge.org/pipermail/rubyinstaller-devel/2008-April/000277.html

Hope that helps,

Gordon

From rogerpack2005 at gmail.com  Thu Jun  5 18:41:55 2008
From: rogerpack2005 at gmail.com (Roger Pack)
Date: Thu, 5 Jun 2008 16:41:55 -0600
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <71166b3b0806040847i62726fa6ue8a3be832479355d@mail.gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
	<71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
	<E581A151-26E9-427F-A8E2-EC6EA1C0F7E9@gmail.com>
	<71166b3b0806040847i62726fa6ue8a3be832479355d@mail.gmail.com>
Message-ID: <0E8BF849-E5DB-4124-85DF-1528EDAA6A57@gmail.com>

Probably could use a 'readme' in there on how to set it up :) [like  
you need to add it to the path, then run the tests, and you need to  
merge the rubygems directory into the main to use gems].

I think what would be nice would be to have a package that includes  
the devkit.
Maybe call it win32 power bundle or something, so that people can  
build things like mongrel, on the fly, if they want to.  Then it could  
include those nice .cmd's for gcc and make or what not.  You might  
have to warn people that it will be using those instead of their  
cygwin versions, but power users won't mind that.  Ideally, you'd want  
it to be able to use the mingw versions whenever you are running a gem  
command, hence my suggesting that you bundle gems with  
gem_with_mingw_path.cmd # sets up the paths right for compilation


Could also offer the 'normal' OCI for mingw, too.
GL!
-R

On Jun 4, 2008, at 9:47 AM, Luis Lavena wrote:

> On Wed, Jun 4, 2008 at 11:12 AM, Roger Pack  
> <rogerpack2005 at gmail.com> wrote:
>> if you get time, could I get a copy of the build that results in  
>> 'only a
>> few' errors
>> as you mentioned, and outputs its errors here
>>
>> http://dump.mmediasys.com/installer3/
>> ?
>>
>
> http://dump.mmediasys.com/installer3/ruby-1.8.6-p114-i386- 
> mingw32-2.txt
>
> What I needed to do was merge both ruby_mingw and rubygems_mingw since
> was splitted for MSI setup creation.
>
>> I wonder if it differs from mine somehow.
>> Did it have openssl installed and run those tests, too?
>
> I used the the same version of ruby I'm distributing to test, and
> actually the tests run on top of this version and not the installed
> one.
> (dunno if that's clear, let me rephrase: tests uses the sandbox ruby
> version, not the one you used to build the sandbox).
>
> If test are failing that means something hacked your PATH because the
> test add the sandboxed ruby _before_ anything else, so if there is an
> openssl dll, will find it there first.
>
> -- 
> Luis Lavena
> AREA 17
> -
> Human beings, who are almost unique in having the ability to learn  
> from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel


From luislavena at gmail.com  Thu Jun  5 18:57:43 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 6 Jun 2008 00:57:43 +0200
Subject: [Rubyinstaller-devel] mingw openssl test failure
In-Reply-To: <0E8BF849-E5DB-4124-85DF-1528EDAA6A57@gmail.com>
References: <966599840806031544i49218bb0t91cb49e1e9668d53@mail.gmail.com>
	<71166b3b0806031554r6f3c1c98ta971309f4537c77e@mail.gmail.com>
	<E581A151-26E9-427F-A8E2-EC6EA1C0F7E9@gmail.com>
	<71166b3b0806040847i62726fa6ue8a3be832479355d@mail.gmail.com>
	<0E8BF849-E5DB-4124-85DF-1528EDAA6A57@gmail.com>
Message-ID: <71166b3b0806051557j75a74082u1449764e43dffeb8@mail.gmail.com>

On Fri, Jun 6, 2008 at 12:41 AM, Roger Pack <rogerpack2005 at gmail.com> wrote:
> Probably could use a 'readme' in there on how to set it up :) [like you need
> to add it to the path, then run the tests, and you need to merge the
> rubygems directory into the main to use gems].
>

There is a readme, there was a lot of discussion here and over
ruby-talk about how to use it.

To run the test it automatically add the sandboxed ruby in the path,
you don't need to do it manually. Also to run the tests there is no
need to have rubygems into the sandboxed ruby.

> I think what would be nice would be to have a package that includes the
> devkit.

There is, like I posted in my blog and several times over the mailing
list, it's available in the dump url:

http://dump.mmediasys.com/installer3/

look for the sandbox-mingw-msys 7z package, is the latest version used
to build that version of ruby.

> Maybe call it win32 power bundle or something, so that people can build
> things like mongrel, on the fly, if they want to.  Then it could include
> those nice .cmd's for gcc and make or what not.  You might have to warn
> people that it will be using those instead of their cygwin versions, but
> power users won't mind that.  Ideally, you'd want it to be able to use the
> mingw versions whenever you are running a gem command, hence my suggesting
> that you bundle gems with gem_with_mingw_path.cmd # sets up the paths right
> for compilation
>

Don't take this harsh but stop putting name to stuff and use it or
create something.

Again on the "gem_with_mingw" feel free to create whatever works for
you, share with the community and get feedback, that's the only way a
theory can prove to be useful or totally useless.

For me, the gcc, make and sh bat files make rubygems tests pass, also
make mongrel and other gems painless to build without tweaking the
path.

You should keep in mind this is not a package for average joe ruby,
this is a package for ruby developers/hackers and gem creators to
provide feedback about MinGW compatibility. There are a lot of task
that must be done before it can be massively used.

Gordon generously took the time to collect and update the wiki with the Roadmap:

http://rubyinstaller.rubyforge.org/wiki/wiki.pl?Roadmap

Feel free to contribute on some of these task since most of them are priority.

>
> Could also offer the 'normal' OCI for mingw, too.

By normal you mean what?

With this version of One-Click we are trying to avoid the mistakes did
on the first place. I wouldn't not invest time on something that in
the long run will be dropped (like a NSIS or InnoSetup script) or
cannot be easily manageable.

Also the approach to bundle everything is not part of our goal right
now. In any case only gems and extensions bundled in gems will be the
only components that will be part of this, mainly because they have a
mechanism to manage them, on the contrary of normal "setup.rb"
extensions.

There is a lot of discussion about RUBY_PLATFORM, changes between
implementations and fixes for the underlying Ruby code to reduce the
incompatibilities between platforms, so we have our hands busy right
now, feel free to fork and contribute with your ideas and experiments,
I'm eager to see what cool ideas can you bring to this project.

Regards,
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From gthiesfeld at gmail.com  Thu Jun  5 18:58:33 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Thu, 5 Jun 2008 17:58:33 -0500
Subject: [Rubyinstaller-devel] Bug in Ruby File#open
Message-ID: <e9ece6840806051558p791e827fs885be552f6659f0d@mail.gmail.com>

I've been running the rubyspecs[1] against Ruby 1.8.6 Mingw for the
past few days, and I think I've found a bug in File#open.

>> File.open('test'){} # create the file
=> nil
>> File.open('test', File::TRUNC)
Errno::EINVAL: Invalid argument - test
        from (irb):3:in `initialize'
        from (irb):3:in `open'
        from (irb):3
>>

That doesn't happen on linux

irb(main):002:0> File.open('test','w'){}
=> nil
irb(main):003:0> File.open('test',File::TRUNC)
=> #<File:test>

I'm hoping someone can point me in the right direction to track this
down.  Bug submissions without patches attached don't seem to get
fixed ;-)  I looked at file.c and io.c until my eyes bled, and
couldn't make heads or tails.

[1] http://rubyspec.org

Thanks,

Gordon

From luislavena at gmail.com  Thu Jun  5 19:24:49 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 6 Jun 2008 01:24:49 +0200
Subject: [Rubyinstaller-devel] Bug in Ruby File#open
In-Reply-To: <e9ece6840806051558p791e827fs885be552f6659f0d@mail.gmail.com>
References: <e9ece6840806051558p791e827fs885be552f6659f0d@mail.gmail.com>
Message-ID: <71166b3b0806051624p2aaa734geafede9d3a26e17b@mail.gmail.com>

On Fri, Jun 6, 2008 at 12:58 AM, Gordon Thiesfeld <gthiesfeld at gmail.com> wrote:
> I've been running the rubyspecs[1] against Ruby 1.8.6 Mingw for the
> past few days, and I think I've found a bug in File#open.
>
>>> File.open('test'){} # create the file
> => nil
>>> File.open('test', File::TRUNC)
> Errno::EINVAL: Invalid argument - test
>        from (irb):3:in `initialize'
>        from (irb):3:in `open'
>        from (irb):3
>>>
>
> That doesn't happen on linux
>
> irb(main):002:0> File.open('test','w'){}
> => nil
> irb(main):003:0> File.open('test',File::TRUNC)
> => #<File:test>
>
> I'm hoping someone can point me in the right direction to track this
> down.  Bug submissions without patches attached don't seem to get
> fixed ;-)  I looked at file.c and io.c until my eyes bled, and
> couldn't make heads or tails.
>

Wow, did I miss a mail to ruby-core? (or was rubyforge tracker?)

Anyway, nice finding, replicated the same on both VC and MinGW builds,
1.8.5 and 1.8.6 code.

Just pinned this for work during lunch tomorrow, this is a tricky one
since File.open is actually calling IO.open (it's being included) --
will be hard but not impossible to track down.

Will let you know my findings!

Keep those bugs coming Gordon, I silently keep an eye on the
changesets feed for rubyspec and see all the great work you're doing!
:-)

Take care and talk tomorrow!
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From rogerpack2005 at gmail.com  Thu Jun  5 19:48:41 2008
From: rogerpack2005 at gmail.com (Roger Pack)
Date: Thu, 5 Jun 2008 17:48:41 -0600
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <71166b3b0806051602h337c9888t597a670a94dfbcd6@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<966599840806031208s32531032i36b48fd8b5c80e33@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<EC9D202B-1EE3-4BFD-90C3-AF068749D099@gmail.com>
	<966599840806051552r197af612v3b80e0aed1eb5411@mail.gmail.com>
	<71166b3b0806051602h337c9888t597a670a94dfbcd6@mail.gmail.com>
Message-ID: <A5F15204-EBFD-4BE7-93F1-0DA586EBAB40@gmail.com>

> Is not a window bug "per se" but a implementation bug of
> Ruby+MinGW+Readline, can't complicated to explain, so feel free to dig
> into my mails and look by yourself.
>
> Again: these ports don't sole the issue, but why you don't ask them
> and see what they answer?
>
>> Or, as you did before, just release it with the [working] readline.so
>> compiled by MSVC 6 :)
>
> Again, the test halting is not a problem, only for automated testing,
> again you missed the whole point.
>
> The readline.so build with MSVC6 segfaul on MinGW Ruby, plain as  
> simple.

I was trying to remember an email sent once to ruby-talk [not the  
sandbox one] where you mentioned a "pre-release" of mingw, which  
passed all the tests.  So I was suggesting [as you already knew] to  
just use that one :)
>> Take care!


> To run the test it automatically add the sandboxed ruby in the path,
> you don't need to do it manually. Also to run the tests there is no
> need to have rubygems into the sandboxed ruby.
sounds like you're on the right path, then.  I was just confused as it  
had changed since the last time I downloaded the sandbox.
>
> http://dump.mmediasys.com/installer3/
yep that's the one.  Except now I just use a git-clone of the repo, as  
per your suggestion.

> For me, the gcc, make and sh bat files make rubygems tests pass, also
> make mongrel and other gems painless to build without tweaking the
> path.

Sure.  My only fear is that they'll clash with cygwin on some users'  
machines.  Barring that they'll work as good as any, esp. with your  
patch idea.

>
> Gordon generously took the time to collect and update the wiki with  
> the Roadmap:
>
> http://rubyinstaller.rubyforge.org/wiki/wiki.pl?Roadmap

Looks great.
>
>> Could also offer the 'normal' OCI for mingw, too.
>
> By normal you mean what?

The one you plan on releasing, apparently.  now that I realize there's  
a gem in the works then my comments are moot.
>
> With this version of One-Click we are trying to avoid the mistakes did
> on the first place. I wouldn't not invest time on something that in
> the long run will be dropped (like a NSIS or InnoSetup script) or
> cannot be easily manageable.
Do you think the IO redirection problem will become a big problem ever?

>
> Also the approach to bundle everything is not part of our goal right
> now. In any case only gems and extensions bundled in gems will be the
> only components that will be part of this, mainly because they have a
> mechanism to manage them, on the contrary of normal "setup.rb"
> extensions.
sounds good.
>
> There is a lot of discussion about RUBY_PLATFORM, changes between
> implementations and fixes for the underlying Ruby code to reduce the
> incompatibilities between platforms, so we have our hands busy right
> now, feel free to fork and contribute with your ideas and experiments,
> I'm eager to see what cool ideas can you bring to this project.
Do you have any links for these discussions?  I know my own idea on it  
was rapidly shot down :)
One thought I had was to tell the facets people to implement something  
that yielded something like [Python's?]
require 'facets'
 > OS.os
  => 'windows' # or :windows
 > OS.compiler
  => 'mingw'
 > OS.bits
  => 64

But that would be somewhat kludgey.  I'm not sure why core seems  
reluctant to make simplifying changes. :)
-R

From gthiesfeld at gmail.com  Thu Jun  5 19:51:33 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Thu, 5 Jun 2008 18:51:33 -0500
Subject: [Rubyinstaller-devel] Bug in Ruby File#open
In-Reply-To: <71166b3b0806051624p2aaa734geafede9d3a26e17b@mail.gmail.com>
References: <e9ece6840806051558p791e827fs885be552f6659f0d@mail.gmail.com>
	<71166b3b0806051624p2aaa734geafede9d3a26e17b@mail.gmail.com>
Message-ID: <e9ece6840806051651p26ba7ef5g2e798d94ad848c99@mail.gmail.com>

On Thu, Jun 5, 2008 at 6:24 PM, Luis Lavena <luislavena at gmail.com> wrote:

> Wow, did I miss a mail to ruby-core? (or was rubyforge tracker?)

No, I haven't submitted anything yet.  I wanted to try to track down
the cause, and maybe have a patch to submit with the bug.  I suppose
an email to ruby-core couldn't hurt, though...

>
> Will let you know my findings!

Great, thanks!

Gordon

From luislavena at gmail.com  Fri Jun  6 03:13:52 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 6 Jun 2008 04:13:52 -0300
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <A5F15204-EBFD-4BE7-93F1-0DA586EBAB40@gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<EC9D202B-1EE3-4BFD-90C3-AF068749D099@gmail.com>
	<966599840806051552r197af612v3b80e0aed1eb5411@mail.gmail.com>
	<71166b3b0806051602h337c9888t597a670a94dfbcd6@mail.gmail.com>
	<A5F15204-EBFD-4BE7-93F1-0DA586EBAB40@gmail.com>
Message-ID: <71166b3b0806060013i665754b2u59dfb3ece6e3beeb@mail.gmail.com>

On Thu, Jun 5, 2008 at 8:48 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
>> Is not a window bug "per se" but a implementation bug of
>> Ruby+MinGW+Readline, can't complicated to explain, so feel free to dig
>> into my mails and look by yourself.
>>
>> Again: these ports don't sole the issue, but why you don't ask them
>> and see what they answer?
>>
>>> Or, as you did before, just release it with the [working] readline.so
>>> compiled by MSVC 6 :)
>>
>> Again, the test halting is not a problem, only for automated testing,
>> again you missed the whole point.
>>
>> The readline.so build with MSVC6 segfaul on MinGW Ruby, plain as simple.
>
> I was trying to remember an email sent once to ruby-talk [not the sandbox
> one] where you mentioned a "pre-release" of mingw, which passed all the
> tests.  So I was suggesting [as you already knew] to just use that one :)

I asked in ruby-core about some tests that seems to always fails (at
least on windows) there was 3 of them, so we can say it was labeled
"all tests passes".

>> To run the test it automatically add the sandboxed ruby in the path,
>> you don't need to do it manually. Also to run the tests there is no
>> need to have rubygems into the sandboxed ruby.
>
> sounds like you're on the right path, then.  I was just confused as it had
> changed since the last time I downloaded the sandbox.

Yeah, you can see most of the changes are documented into the
changelog file or in the commits logs.

>>
>> http://dump.mmediasys.com/installer3/
>
> yep that's the one.  Except now I just use a git-clone of the repo, as per
> your suggestion.
>

The git one contains the source code to build everything, and the
files in the dump sections are packages of that stuff "pre-baked" with
some patches that we sent to ruby-core and got merged in.

>> For me, the gcc, make and sh bat files make rubygems tests pass, also
>> make mongrel and other gems painless to build without tweaking the
>> path.
>
> Sure.  My only fear is that they'll clash with cygwin on some users'
> machines.  Barring that they'll work as good as any, esp. with your patch
> idea.
>

Unless they have cygwin in the path I don't see a clash there, some
user uses the cygwin-like console like some guys use the MSYS one, so
is not usually in the PATH.

>>
>>> Could also offer the 'normal' OCI for mingw, too.
>>
>> By normal you mean what?
>
> The one you plan on releasing, apparently.  now that I realize there's a gem
> in the works then my comments are moot.

Again: there will not be a "gem" for the compiler and supporting tools
for GCC, there will be a installer, just like the one we are building
for the Runtime itself.

All the addons or extensions will be added using rubygems as manager
to avoid leave files "orphaned" between updates.

>>
>> With this version of One-Click we are trying to avoid the mistakes did
>> on the first place. I wouldn't not invest time on something that in
>> the long run will be dropped (like a NSIS or InnoSetup script) or
>> cannot be easily manageable.
>
> Do you think the IO redirection problem will become a big problem ever?
>

Haven't encountered anyone with this problem, but never heard back
from ruby-core about this behavior.

>>
>> Also the approach to bundle everything is not part of our goal right
>> now. In any case only gems and extensions bundled in gems will be the
>> only components that will be part of this, mainly because they have a
>> mechanism to manage them, on the contrary of normal "setup.rb"
>> extensions.
>
> sounds good.
>>
>> There is a lot of discussion about RUBY_PLATFORM, changes between
>> implementations and fixes for the underlying Ruby code to reduce the
>> incompatibilities between platforms, so we have our hands busy right
>> now, feel free to fork and contribute with your ideas and experiments,
>> I'm eager to see what cool ideas can you bring to this project.
>
> Do you have any links for these discussions?  I know my own idea on it was
> rapidly shot down :)

The RUBY_PLATFORM stuff is about to be standarized:

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/17116

But there should be some discussion about it that I didn't had time to
tackle and shoot my thoughts about it.

I can collect some of the mailing lists posts but you must indulge me
since I'm getting used to a new timezone and working hours (just
arrived to Paris 2 days ago)... let me collect that during the
weekend.

> One thought I had was to tell the facets people to implement something that
> yielded something like [Python's?]
> require 'facets'
>> OS.os
>  => 'windows' # or :windows
>> OS.compiler
>  => 'mingw'
>> OS.bits
>  => 64

Similar to the stuff the Platform gem is providing right now, and too
similar to what Rubinius guys did (Rubinius::COMPILER)

>
> But that would be somewhat kludgey.  I'm not sure why core seems reluctant
> to make simplifying changes. :)

I think that will be rejected even before you hit send. But maybe we
can all workout some sort of solution. In any case, will look into
that topic after get some feedback about RUBY_PLATFORM discussion.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From rogerpack2005 at gmail.com  Fri Jun  6 10:43:17 2008
From: rogerpack2005 at gmail.com (Roger Pack)
Date: Fri, 6 Jun 2008 08:43:17 -0600
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <71166b3b0806060013i665754b2u59dfb3ece6e3beeb@mail.gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<71166b3b0806031342g8cae7dfo6c5b61d1b765963c@mail.gmail.com>
	<966599840806031352w11cc548bif4f2663eb6167e98@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<EC9D202B-1EE3-4BFD-90C3-AF068749D099@gmail.com>
	<966599840806051552r197af612v3b80e0aed1eb5411@mail.gmail.com>
	<71166b3b0806051602h337c9888t597a670a94dfbcd6@mail.gmail.com>
	<A5F15204-EBFD-4BE7-93F1-0DA586EBAB40@gmail.com>
	<71166b3b0806060013i665754b2u59dfb3ece6e3beeb@mail.gmail.com>
Message-ID: <1BC77304-72F9-46DC-9C22-D215A6CD1260@gmail.com>

>> I was trying to remember an email sent once to ruby-talk [not the  
>> sandbox
>> one] where you mentioned a "pre-release" of mingw, which passed all  
>> the
>> tests.  So I was suggesting [as you already knew] to just use that  
>> one :)
>

I'm  having trouble finding an email where you had mentioned "this  
isn't even a release" but it was like stage 2 of the 'get your hands  
dirty' email series.  Does this ring a bell in any way shape or  
form?   Am I just making things up? :)

> Yeah, you can see most of the changes are documented into the
> changelog file or in the commits logs.
thanks

> Again: there will not be a "gem" for the compiler and supporting tools
> for GCC, there will be a installer, just like the one we are building
> for the Runtime itself.

It seems like there already is an 'install' for gem developers.  The  
installer3.  That worked for the rmagick people, at least, and also  
for a friend of mine who compiled eventmachine on it [eventually, once  
he figured out that the paths had to be a certain style].


>>
>> Do you think the IO redirection problem will become a big problem  
>> ever?
>>
>
> Haven't encountered anyone with this problem, but never heard back
> from ruby-core about this behavior.

I wonder if it's caused by readline reading always from stdin [well,  
obviously that's the case], but I wonder if they do it poorly.  Oh  
well if it's a minor bug then... :)  The looping cpu thing is a  
concern, it seems.  Was that ever fixed?

-R

PS

[If I ever get time, I wonder if something along the following lines  
would be interesting:
1) install the marvelous mingw package distributed by OCI.
2) install the devkit package distributed by OCI.
# now here's the fun part:
3) gem install mingw_imagemagick_headers # or gem install  
mingw_imagemagick_binaries
5) gem install mingw_openssl_src # or gem update
4) gem install mingw_git # or mingw_xming, or mingw_...

i.e. use ruby gems as an apt-get style system for mingw progs, since  
that is very lacking for mingw, or is it?  I'm not sure. They  
definitely lack something of ease. :)
But I guess the first step is the packages noted on the roadmap.
This way end users don't have to be developers.  You can just have  
rubygems dependencies which simplify installation.  Of course, this is  
for non ruby apps, but hey :) Just thinking out loud :)

From luislavena at gmail.com  Fri Jun  6 11:07:58 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 6 Jun 2008 17:07:58 +0200
Subject: [Rubyinstaller-devel] my old gripe :)
In-Reply-To: <1BC77304-72F9-46DC-9C22-D215A6CD1260@gmail.com>
References: <966599840806031155h1b7009e6s1a8fa846431da9ec@mail.gmail.com>
	<71166b3b0806031410k31e41ae0i88b427bd44d35188@mail.gmail.com>
	<966599840806031600n50c16553k89cc3b5b87f58e09@mail.gmail.com>
	<71166b3b0806031607j61651149yfcc52c951aeaa89e@mail.gmail.com>
	<EC9D202B-1EE3-4BFD-90C3-AF068749D099@gmail.com>
	<966599840806051552r197af612v3b80e0aed1eb5411@mail.gmail.com>
	<71166b3b0806051602h337c9888t597a670a94dfbcd6@mail.gmail.com>
	<A5F15204-EBFD-4BE7-93F1-0DA586EBAB40@gmail.com>
	<71166b3b0806060013i665754b2u59dfb3ece6e3beeb@mail.gmail.com>
	<1BC77304-72F9-46DC-9C22-D215A6CD1260@gmail.com>
Message-ID: <71166b3b0806060807v4e493db1k40c5fa2aa099eb6b@mail.gmail.com>

On Fri, Jun 6, 2008 at 4:43 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
>>> I was trying to remember an email sent once to ruby-talk [not the sandbox
>>> one] where you mentioned a "pre-release" of mingw, which passed all the
>>> tests.  So I was suggesting [as you already knew] to just use that one :)
>>
>
> I'm  having trouble finding an email where you had mentioned "this isn't
> even a release" but it was like stage 2 of the 'get your hands dirty' email
> series.  Does this ring a bell in any way shape or form?   Am I just making
> things up? :)
>

http://blog.mmediasys.com/2008/05/24/random-bits-and-experiments/

Almost before the post end:

"but still will try to keep my pace with rubyinstaller and code some
stuff to do a proper release of new One-Click Installer (yeah, we all
know that a .7z file is not a release)."

There is also an explanation of what this "sandbox" stuff is aimed to:

http://github.com/luislavena/rubyinstaller/tree/master/README.txt

>> Again: there will not be a "gem" for the compiler and supporting tools
>> for GCC, there will be a installer, just like the one we are building
>> for the Runtime itself.
>
> It seems like there already is an 'install' for gem developers.  The
> installer3.  That worked for the rmagick people, at least, and also for a
> friend of mine who compiled eventmachine on it [eventually, once he figured
> out that the paths had to be a certain style].
>

Actually is no "install", it's a "developer sandbox" version of ruby
that preps the environment to work and develop the One-Click Installer
itself, as I commented in the "Get your hands dirty" post. It's aimed
to developers and gem creators that want to see if they tool can work
on MinGW, since most of the latest development and compatibility stuff
happened just for VC, leaving MinGW behind for a lot of time.


>
>>>
>>> Do you think the IO redirection problem will become a big problem ever?
>>>
>>
>> Haven't encountered anyone with this problem, but never heard back
>> from ruby-core about this behavior.
>
> I wonder if it's caused by readline reading always from stdin [well,
> obviously that's the case], but I wonder if they do it poorly.  Oh well if
> it's a minor bug then... :)  The looping cpu thing is a concern, it seems.
>  Was that ever fixed?
>

The CPU usage is not a bug of readline itself, but was fixed in ruby
code in repository, is the w32_rb_select pooling mechanism that
interferes with some Antivirus software. Change or disable your
antirivus and that problem will go away :-P

>
> [If I ever get time, I wonder if something along the following lines would
> be interesting:
> 1) install the marvelous mingw package distributed by OCI.
> 2) install the devkit package distributed by OCI.
> # now here's the fun part:
> 3) gem install mingw_imagemagick_headers # or gem install
> mingw_imagemagick_binaries
> 5) gem install mingw_openssl_src # or gem update
> 4) gem install mingw_git # or mingw_xming, or mingw_...
>

I don't know what you meant with this. Git already have it's own
installer. double package stuff into rubygems is not the purpose of
Rubygems. RubyGems is not a general packaging software, it just to
ease the distribution of libraries and extensions *for Ruby*, not your
operating system.

The "Runtime" part of OCI will be a Windows Installer, so it can be
easily patched with just creating differences across .msi packages.
The same will happen for Developer Kit, as I explained several times.

The thing with RMagick is the way the work with ImageMagick DLL
instead of some statically linked libraries, like wxRuby guys did and
which seems to work ok.

> i.e. use ruby gems as an apt-get style system for mingw progs, since that is
> very lacking for mingw, or is it?  I'm not sure. They definitely lack
> something of ease. :)

apt-get is not the holy grail, you need to leverage in the own OS
tools, so sysadmins of Windows feel confortable to deploy ruby in
corporate environments. Apt-get for windows sounds as bad idea for
them, trust me.

> But I guess the first step is the packages noted on the roadmap.
> This way end users don't have to be developers.  You can just have rubygems
> dependencies which simplify installation.  Of course, this is for non ruby
> apps, but hey :) Just thinking out loud :)

I like to think, but also to experiment, you can try experimenting and
create stuff, doesn't matter if they work out of the box, the
important thing is that you discover truly if they are useful or not,
and get feedback.

Regards,
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From gthiesfeld at gmail.com  Fri Jun 20 14:35:16 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Fri, 20 Jun 2008 13:35:16 -0500
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
Message-ID: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>

With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
upcoming RubyGems 1.2.0[2] release, I've worked some on updating
installer3.  The changes are in my github repo[3]

Below are a list of issues that I have.  I'd like some feedback from
anyone out there that's paying attention ;-D  Any ways to improve what
I'm doing?  Anything I'm missing?

Iconv issue

	Which package do we need to switch to?
	
Wix issues

	Need to write paraffin tasks

		The steps Luis used to generate the wxs frgaments are documented in
the comments of wix.rake.  I just haven't gotten around to it yet.

	Paraffin updates, but `rake package` fails

		I can update the .wxs files using the steps Luis laid out, but wix
errors out when it's run.  Not sure what's going on here. light.exe is
throwing some odd errors [4].

 	Need a gui

		Once wxs fragments issue gets straightened out, we still need to
build a gui for the installer

Mingw, Msys issues

	Needs wxs files generated
 	
 	Need a task to add batch files to %rubypath%\bin
 	
		make.bat, gcc.bat, sh.bat
  	
[1]  http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/eaa4ab03127fd4b9#
[2]  http://rubyforge.org/pipermail/rubygems-developers/2008-June/003892.html
[3]  http://github.com/vertiginous/rubyinstaller
[4] http://pastie.org/219031

Thanks,

Gordon

From rogerpack2005 at gmail.com  Fri Jun 20 14:48:30 2008
From: rogerpack2005 at gmail.com (Roger Pack)
Date: Fri, 20 Jun 2008 12:48:30 -0600
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
Message-ID: <966599840806201148u66aace9dl764e9a1b453c9d54@mail.gmail.com>

> Iconv issue
>
>        Which package do we need to switch to?
Apparently it's non-trivial, but you can compile your own DLL with mingw.
http://wiki.rubyonrails.org/rails/pages/Win32MingwInstall [sorry it's messy].

Are you planning on releasing mingw or win32?
GL!
-R

From luislavena at gmail.com  Fri Jun 20 15:13:40 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 20 Jun 2008 21:13:40 +0200
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <966599840806201148u66aace9dl764e9a1b453c9d54@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
	<966599840806201148u66aace9dl764e9a1b453c9d54@mail.gmail.com>
Message-ID: <71166b3b0806201213p40b03184w2247c74047794ccb@mail.gmail.com>

On Fri, Jun 20, 2008 at 8:48 PM, Roger Pack <rogerpack2005 at gmail.com> wrote:
>> Iconv issue
>>
>>        Which package do we need to switch to?
> Apparently it's non-trivial, but you can compile your own DLL with mingw.
> http://wiki.rubyonrails.org/rails/pages/Win32MingwInstall [sorry it's messy].
>

Yeah, and confusing! :-P

> Are you planning on releasing mingw or win32?

Dunno what you mean... releasing what?

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From luislavena at gmail.com  Fri Jun 20 15:18:18 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 20 Jun 2008 21:18:18 +0200
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
Message-ID: <71166b3b0806201218ned34dbldbde78b60979ffdc@mail.gmail.com>

On Fri, Jun 20, 2008 at 8:35 PM, Gordon Thiesfeld <gthiesfeld at gmail.com> wrote:
> With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
> upcoming RubyGems 1.2.0[2] release, I've worked some on updating
> installer3.  The changes are in my github repo[3]
>
> Below are a list of issues that I have.  I'd like some feedback from
> anyone out there that's paying attention ;-D  Any ways to improve what
> I'm doing?  Anything I'm missing?
>
> Iconv issue
>
>        Which package do we need to switch to?
>

We should revert from win-iconv to gnuwin32 iconv version:

http://gnuwin32.sourceforge.net/packages/libiconv.htm

We need binaries and dependencies.

> Wix issues
>
>        Need to write paraffin tasks
>
>                The steps Luis used to generate the wxs frgaments are documented in
> the comments of wix.rake.  I just haven't gotten around to it yet.
>
>        Paraffin updates, but `rake package` fails
>
>                I can update the .wxs files using the steps Luis laid out, but wix
> errors out when it's run.  Not sure what's going on here. light.exe is
> throwing some odd errors [4].
>

I'll verify it but there is no need to copy the wxs fragments into
sandbox to work. I used the relative references as workaround.

>        Need a gui
>
>                Once wxs fragments issue gets straightened out, we still need to
> build a gui for the installer
>

Yeah, didn't had time to work on that yet.

> Mingw, Msys issues
>
>        Needs wxs files generated
>

Yes, each one for each gcc package, maybe we would handle those
manually based on the version, but will not be part of the automated
process (dunno yet, we need to talk a bit about it).

>        Need a task to add batch files to %rubypath%\bin
>
>                make.bat, gcc.bat, sh.bat
>

These files should be fit better into "resources", I'll work on that
after the MinGW stuff.

> [1]  http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/eaa4ab03127fd4b9#
> [2]  http://rubyforge.org/pipermail/rubygems-developers/2008-June/003892.html
> [3]  http://github.com/vertiginous/rubyinstaller
> [4] http://pastie.org/219031
>
> Thanks,
>

Thanks to you Gordon, I'll check all that today!
(still owe you a ruby bugfix). ;-)
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From gthiesfeld at gmail.com  Fri Jun 20 15:48:29 2008
From: gthiesfeld at gmail.com (Gordon Thiesfeld)
Date: Fri, 20 Jun 2008 14:48:29 -0500
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <71166b3b0806201218ned34dbldbde78b60979ffdc@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
	<71166b3b0806201218ned34dbldbde78b60979ffdc@mail.gmail.com>
Message-ID: <e9ece6840806201248p1463eca1ib60c427ac8b6fc6@mail.gmail.com>

On Fri, Jun 20, 2008 at 2:18 PM, Luis Lavena <luislavena at gmail.com> wrote:
> On Fri, Jun 20, 2008 at 8:35 PM, Gordon Thiesfeld <gthiesfeld at gmail.com> wrote:
>> With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
>> upcoming RubyGems 1.2.0[2] release, I've worked some on updating
>> installer3.  The changes are in my github repo[3]
>>
>> Below are a list of issues that I have.  I'd like some feedback from
>> anyone out there that's paying attention ;-D  Any ways to improve what
>> I'm doing?  Anything I'm missing?
>>
>> Iconv issue
>>
>>        Which package do we need to switch to?
>>
>
> We should revert from win-iconv to gnuwin32 iconv version:
>
> http://gnuwin32.sourceforge.net/packages/libiconv.htm
>
> We need binaries and dependencies.

I'm updating this now.

>
>> Wix issues
>>
>>        Need to write paraffin tasks
>>
>>                The steps Luis used to generate the wxs frgaments are documented in
>> the comments of wix.rake.  I just haven't gotten around to it yet.
>>
>>        Paraffin updates, but `rake package` fails
>>
>>                I can update the .wxs files using the steps Luis laid out, but wix
>> errors out when it's run.  Not sure what's going on here. light.exe is
>> throwing some odd errors [4].
>>
>
> I'll verify it but there is no need to copy the wxs fragments into
> sandbox to work. I used the relative references as workaround.
>

I did this so that people could hack on the wxs file and still have
the original, but there are two problems with this. First, that's what
a VCS is for, and second, the rake package task overwrites them with
the original everytime anyway.  I will fix.

>>        Need a gui
>>
>>                Once wxs fragments issue gets straightened out, we still need to
>> build a gui for the installer
>>
>
> Yeah, didn't had time to work on that yet.

Yeah, neither did I ;-)  Just trying to keep track of what's left to do.

>
>> Mingw, Msys issues
>>
>>        Needs wxs files generated
>>
>
> Yes, each one for each gcc package, maybe we would handle those
> manually based on the version, but will not be part of the automated
> process (dunno yet, we need to talk a bit about it).
>
>>        Need a task to add batch files to %rubypath%\bin
>>
>>                make.bat, gcc.bat, sh.bat
>>
>
> These files should be fit better into "resources", I'll work on that
> after the MinGW stuff.

I'm just trying to think through the process of how these scripts
would get packaged.  I'm thinking something similar to the way you
have rubygems set up as fragment (is that the correct term?).


>
>> [1]  http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/eaa4ab03127fd4b9#
>> [2]  http://rubyforge.org/pipermail/rubygems-developers/2008-June/003892.html
>> [3]  http://github.com/vertiginous/rubyinstaller
>> [4] http://pastie.org/219031
>>
>> Thanks,
>>
>
> Thanks to you Gordon, I'll check all that today!
> (still owe you a ruby bugfix). ;-)
> --
> Luis Lavena
> AREA 17
> -
> Human beings, who are almost unique in having the ability to learn from
> the experience of others, are also remarkable for their apparent
> disinclination to do so.
> Douglas Adams
> _______________________________________________
> Rubyinstaller-devel mailing list
> Rubyinstaller-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rubyinstaller-devel
>

From roger.pack at leadmediapartners.com  Fri Jun 20 16:23:17 2008
From: roger.pack at leadmediapartners.com (Roger Pack)
Date: Fri, 20 Jun 2008 14:23:17 -0600
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <71166b3b0806201213p40b03184w2247c74047794ccb@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
	<966599840806201148u66aace9dl764e9a1b453c9d54@mail.gmail.com>
	<71166b3b0806201213p40b03184w2247c74047794ccb@mail.gmail.com>
Message-ID: <966599840806201323n7ac03a06ve4f54c964a2433ae@mail.gmail.com>

Yeah I left it messy since installer3 came out so nobody needed it anymore :D

>> Are you planning on releasing mingw or win32?
>
> Dunno what you mean... releasing what?

My question is if this plans to be an "official" mingw release.  I
guess now is as good a time as any.  Maybe warn people that it may not
be compatible with precompiled existing win32 gems [like if they run
gem install rmagick]?

>With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
>upcoming RubyGems 1.2.0[2] release, I've worked some on updating
>installer3.  The changes are in my github repo[3]

Or whether Gordon was referring to releasing an updated OCI VC6
distro.  Now that I look at it, since he mentioned updating
installer3, I assume it's for mingw only?

Thanks!
-R

From luislavena at gmail.com  Fri Jun 20 17:32:10 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Fri, 20 Jun 2008 23:32:10 +0200
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <966599840806201323n7ac03a06ve4f54c964a2433ae@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
	<966599840806201148u66aace9dl764e9a1b453c9d54@mail.gmail.com>
	<71166b3b0806201213p40b03184w2247c74047794ccb@mail.gmail.com>
	<966599840806201323n7ac03a06ve4f54c964a2433ae@mail.gmail.com>
Message-ID: <71166b3b0806201432r48be5d1rb1e8791c4fd3c8ca@mail.gmail.com>

On Fri, Jun 20, 2008 at 10:23 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> Yeah I left it messy since installer3 came out so nobody needed it anymore :D
>
>>> Are you planning on releasing mingw or win32?
>>
>> Dunno what you mean... releasing what?
>
> My question is if this plans to be an "official" mingw release.  I
> guess now is as good a time as any.  Maybe warn people that it may not
> be compatible with precompiled existing win32 gems [like if they run
> gem install rmagick]?
>

Dunno if is the "official mingw" release. but it will be the One-Click
Installer for Windows "official" version, at least supported by me :-P

There is a clear difference between MinGW and VC6 builds, and I
contribute to make it more clear in latest RubyGems.

So if a binary for RMagick is build with VC6 (mswin32 as platform)
will not be automatically installed by RubyGems, you will require
manual install.

For those users that manually try it, we can't do anything more than
say "that wouldn't work".

>>With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
>>upcoming RubyGems 1.2.0[2] release, I've worked some on updating
>>installer3.  The changes are in my github repo[3]
>
> Or whether Gordon was referring to releasing an updated OCI VC6
> distro.  Now that I look at it, since he mentioned updating
> installer3, I assume it's for mingw only?
>

installer2 is what is now OCI, the latest release is 186-26 which is 1.8.6-p114

Even Ruby-core released p230 I'll not update installer2 since there is
no testing in place and all the extension and gems bundled must be
verified for compatibility.

installer3 is the sandbox for development and creation of the new
One-Click Installer (I should put this on my signature).

So most of the work is right now on installer3 (named rubyinstaller on
github, like the project on rubyforge).

Right now we need to get a UI for the installer, to offer the less
options possible to install the Runtime (Ruby+RubyGems) packages.

If you have some free time, feel free to fork the rubyinstaller
repository at github (like gordon did) and when you're done with your
fixes, improvements or ideas, just send me a pull request! :-)

> Thanks!

Thanks to you, have a nice weekend!
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From luislavena at gmail.com  Sat Jun 21 08:54:56 2008
From: luislavena at gmail.com (Luis Lavena)
Date: Sat, 21 Jun 2008 14:54:56 +0200
Subject: [Rubyinstaller-devel] Ruby 1.86. p230 and RubyGems 1.2.0
In-Reply-To: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
References: <e9ece6840806201135j1cbe8d0fm8ffbda48df00d6d6@mail.gmail.com>
Message-ID: <71166b3b0806210554h4b418089sa10e7f74c8ed6702@mail.gmail.com>

On Fri, Jun 20, 2008 at 8:35 PM, Gordon Thiesfeld <gthiesfeld at gmail.com> wrote:
> With the recent announcement of Ruby 1.8.6 patchlevel 230[1] and the
> upcoming RubyGems 1.2.0[2] release, I've worked some on updating
> installer3.  The changes are in my github repo[3]
>
> Below are a list of issues that I have.  I'd like some feedback from
> anyone out there that's paying attention ;-D  Any ways to improve what
> I'm doing?  Anything I'm missing?
>

I did a test on patchelevel 230 and found a series of errors that
wasn't present before.

I sent a mail to ruby-core ([ruby-core:17364]):

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/17364

Basically Drb test or Drb itself is broken in 230, so I wouldn't
recommend we move forward to that version until heard back from
ruby-core.

Regarding the other stuff I'm about to run RubySpecs for Iconv,
Readline and that and see how "compatible" we are right now.

Good weekend everybody!
-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

From mhodgson at gmail.com  Fri Jun 27 20:15:06 2008
From: mhodgson at gmail.com (Mike Hodgson)
Date: Fri, 27 Jun 2008 20:15:06 -0400
Subject: [Rubyinstaller-devel] Updated VC6 One-Click Installer
Message-ID: <6dae68ac0806271715s3ecc38bdta7485eafd6b5e2c8@mail.gmail.com>

Hi all,

I've been conversing with Luis through e-mail for the last few days,
and he convinced me to post here :)

I was originally just working on this for my own needs, but I have
seen requests for it elsewhere. I've compiled the latest ruby 1.8.6
p114 and applied the patches that the Phusion guys came up with (the
same patch from the mingw version). I've also updated Rubygems to
1.2.0 and Rake to 0.8.1. Everything else is exactly the same as the
186-26 installer.

http://www.mikehodgson.com/ruby186-27-mkh.exe

I'd like some folks here to give it a try and let me know if you find
any serious bugs. If not, I'll release it to the wild over the
weekend. I haven't changed the readme's or anything, but this isn't an
official release, it's just something to hold people over until the
mingw version is released.

Mike