From: Luis Lavena <luislavena@...>
Date: 2008-10-30T21:29:12+09:00
Subject: Re: RubyGems 1.3.1

On Oct 30, 4:48 am, Pit Capitain <pit.capit...@gmail.com> wrote:
> 2008/10/29 Eric Hodel <drbr...@segment7.net>:
>
> > = Announce: RubyGems Release 1.3.1
>
> Thank you for the new version. Unfortunately, bug #19268 isn't
> resolved yet, so a simple "gem update" still fails on many Windows
> installations.
>
> In the bug report, it is suggested to simply continue after an
> installation error. A better solution would be to introduce an
> additional option for the update command ("--native", "--precompiled",
> or something else) to only use gem versions with a precompiled binary.
>
> For example, if I have installed hpricot 0.5 and issue "gem update
> hpricot --native", it should update to hpricot 0.6 but not to hpricot
> 0.6.161.
>

As your point may be valid, introducing a new command not only
requires testing but is too major to be something just for a y.z point
release.

I believe the priorities when installing gems should be 'platform-
specific-one' and then 'ruby', contrary to what we have now (ruby,
then-your-platform).

I invite you bring this discussion to rubygems-developer mailing list
so we can workout something for this.

On a side note, I believe we should directly blame gem maintainers for
neglecting the native builds for the platform. Hopefully when GCC-
based Ruby arrives (I know, too vaporware right now) we would rejoice.

> Regards,
> Pit

Regards,
--
Luis Lavena