From radek.bulat at gmail.com  Wed Jan 14 19:47:03 2009
From: radek.bulat at gmail.com (=?ISO-8859-2?Q?Rados=B3aw_Bu=B3at?=)
Date: Thu, 15 Jan 2009 01:47:03 +0100
Subject: [Rubyinstaller-users] Installer for ruby1.8.7 - any chance?
Message-ID: <de8b82ea0901141647h6d411de8x98cbcc12a50d85c5@mail.gmail.com>

Hello.

Any chance that there will be available Ruby OneClickInstaller for
1.8.7? I would be happy with that.

-- 
Rados?aw Bu?at

From radek.bulat at gmail.com  Thu Jan 15 03:51:35 2009
From: radek.bulat at gmail.com (=?ISO-8859-2?Q?Rados=B3aw_Bu=B3at?=)
Date: Thu, 15 Jan 2009 09:51:35 +0100
Subject: [Rubyinstaller-users] Installer for ruby1.8.7 - any chance?
In-Reply-To: <71166b3b0901141723r17997b9dhfa9970d7eb61acc4@mail.gmail.com>
References: <de8b82ea0901141647h6d411de8x98cbcc12a50d85c5@mail.gmail.com>
	<71166b3b0901141723r17997b9dhfa9970d7eb61acc4@mail.gmail.com>
Message-ID: <de8b82ea0901150051u7cab4861o72da18f01518e84d@mail.gmail.com>

2009/1/15 Luis Lavena <luislavena at gmail.com>:
> 2009/1/14 Rados?aw Bu?at <radek.bulat at gmail.com>:
>> Hello.
>
> Hello there!
>
>> Any chance that there will be available Ruby OneClickInstaller for
>> 1.8.7? I would be happy with that.
>
> Don't want to disappoint you but no.
>
> Please let me explain the point.
>
> Current One-Click Ruby Installer (OCI) is bundle of several parts to
> make Ruby work out of the box in Windows.
>
> Those parts (or components) are around 35 ranging from C extensions
> that need to be compiled to bundled Gems.
>
> All these moving parts needs to be manually tested, which on every
> release take me around 10 hours of work. Even after, new things show
> up.
>
> Some of these components hasn't been updated since 1.8.4 or even
> before, yet still are keep for compatibility between previous
> releases.
>
> 1.8.7 bring several modifications from 1.9 branch, which are not
> compatible with the code of gems, libraries and even C extensions.
>
> This has produced difficult times to developers of projects like
> wxRuby, RMagick and others, since lot of users started to complain of
> such incompatibilities when using their libraries.
>
> I personally had really bad experience using it for my projects and
> reverted back to the safe 1.8.6
>
> As you can imagine, these points are just the tip of the iceberg in
> relation to 1.8.7
>
> Now, what will happen, you may ask?
>
> I've been working, in help with other developers in move OCI from
> Visual C compiler to MinGW. There are plenty of good reasons for the
> move which I've commented several times in my blog[1] and mailing
> lists around the tubes.
>
> Our main target versions of Ruby are 1.8.6 and 1.9.1, since most of
> the gems developers are updating their gems to take advantage of 1.9
> functions at the time they add guards around "1.8.x" code.
>
> Even gem developers ignore 1.8.7 for the above mentioned incompatibilities.
>
> As a closing, contrary to official Ruby site considering 1.8.7 latest
> stable, the development community differs.
>
> I hope this shed some light in the 1.8.7 One-Click Ruby Installer topic.
>
> If you have any particular reasons for 1.8.7 that I'm ignoring, please
> share with us and let's workout a way that we can help you out.
>
> Regards,
>
> [1] http://blog.mmediasys.com
> --
> Luis Lavena
> AREA 17
> -
> Perfection in design is achieved not when there is nothing more to add,
> but rather when there is nothing more to take away.
> Antoine de Saint-Exup?ry
>

Thank you for very deep explanation. I know the difference between
1.8.6 and 1.8.7 but I didn't know how difficult it is to maintain OCI.
How long you think it will take to make OCI for ruby1.9.1 (of course
when it will be released)?


-- 
Rados?aw Bu?at

From luislavena at gmail.com  Thu Jan 15 06:49:59 2009
From: luislavena at gmail.com (Luis Lavena)
Date: Thu, 15 Jan 2009 09:49:59 -0200
Subject: [Rubyinstaller-users] Installer for ruby1.8.7 - any chance?
In-Reply-To: <de8b82ea0901150051u7cab4861o72da18f01518e84d@mail.gmail.com>
References: <de8b82ea0901141647h6d411de8x98cbcc12a50d85c5@mail.gmail.com>
	<71166b3b0901141723r17997b9dhfa9970d7eb61acc4@mail.gmail.com>
	<de8b82ea0901150051u7cab4861o72da18f01518e84d@mail.gmail.com>
Message-ID: <71166b3b0901150349w3c914a53g7172e4a654f7b931@mail.gmail.com>

2009/1/15 Rados?aw Bu?at <radek.bulat at gmail.com>:
> 2009/1/15 Luis Lavena <luislavena at gmail.com>:
>> 2009/1/14 Rados?aw Bu?at <radek.bulat at gmail.com>:
>>> Hello.
>>
>> Hello there!
>>
>>> Any chance that there will be available Ruby OneClickInstaller for
>>> 1.8.7? I would be happy with that.
>>
>> Don't want to disappoint you but no.
>>
>> Please let me explain the point.
>>
>> Current One-Click Ruby Installer (OCI) is bundle of several parts to
>> make Ruby work out of the box in Windows.
>>
>> Those parts (or components) are around 35 ranging from C extensions
>> that need to be compiled to bundled Gems.
>>
>> All these moving parts needs to be manually tested, which on every
>> release take me around 10 hours of work. Even after, new things show
>> up.
>>
>> Some of these components hasn't been updated since 1.8.4 or even
>> before, yet still are keep for compatibility between previous
>> releases.
>>
>> 1.8.7 bring several modifications from 1.9 branch, which are not
>> compatible with the code of gems, libraries and even C extensions.
>>
>> This has produced difficult times to developers of projects like
>> wxRuby, RMagick and others, since lot of users started to complain of
>> such incompatibilities when using their libraries.
>>
>> I personally had really bad experience using it for my projects and
>> reverted back to the safe 1.8.6
>>
>> As you can imagine, these points are just the tip of the iceberg in
>> relation to 1.8.7
>>
>> Now, what will happen, you may ask?
>>
>> I've been working, in help with other developers in move OCI from
>> Visual C compiler to MinGW. There are plenty of good reasons for the
>> move which I've commented several times in my blog[1] and mailing
>> lists around the tubes.
>>
>> Our main target versions of Ruby are 1.8.6 and 1.9.1, since most of
>> the gems developers are updating their gems to take advantage of 1.9
>> functions at the time they add guards around "1.8.x" code.
>>
>> Even gem developers ignore 1.8.7 for the above mentioned incompatibilities.
>>
>> As a closing, contrary to official Ruby site considering 1.8.7 latest
>> stable, the development community differs.
>>
>> I hope this shed some light in the 1.8.7 One-Click Ruby Installer topic.
>>
>> If you have any particular reasons for 1.8.7 that I'm ignoring, please
>> share with us and let's workout a way that we can help you out.
>>
>> Regards,
>>
>> [1] http://blog.mmediasys.com
>> --
>> Luis Lavena
>> AREA 17
>> -
>> Perfection in design is achieved not when there is nothing more to add,
>> but rather when there is nothing more to take away.
>> Antoine de Saint-Exup?ry
>>
>
> Thank you for very deep explanation. I know the difference between
> 1.8.6 and 1.8.7 but I didn't know how difficult it is to maintain OCI.
> How long you think it will take to make OCI for ruby1.9.1 (of course
> when it will be released)?

The new One-Click Ruby Installer for both 1.8.6 and 1.9.1 is aiming
end of January/mid February for the official installers.

I'm working on getting all the involved packages compile properly with MinGW.

The Roadmap is described here:

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

Ruby+RubyGems will be the first package

The Development Kit will follow as a installable gem (commented
previously in the mailing list)

1.9.1 bundles both RubyGems and Rake, so no need for caring about
adding that to it.

Regards,
-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup?ry