From: Luis Lavena <luislavena@...>
Date: 2008-11-16T21:11:46+09:00
Subject: Re: One-Click Ruby Installer project stopped?

On Nov 16, 1:27 am, Dave Thomas <d...@pragprog.com> wrote:
> On Nov 15, 2008, at 11:42 AM, Hugh Sasse wrote:
>
> > Can I suggest you make more "noise" about this, please?  It needs to
> > get out on the Rubyforge site, on the Wiki, and elsewhere.  This is
> > a serious problem affecting open source and community based software,
> > and those who object to this model of development have a strong case
> > when they speak of "abandonware".
>
> One simple suggestion. Change RubyGems in 1.9 so the default value for  
> required_ruby_version is '< 1.9'
>
> Then, existing gems that don't have an explicit value for this (which  
> is probably 99% of them) will not even try to load on 1.9. Their  
> maintainers can at some point test them with 1.9 and then add the  
> required_ruby_version line which will make them work again (with both  
> 1.8 and 1.9).
>
> This will also help rubyforge—it can display a 1.9 icon next to gems  
> that have the appropriate Ruby version set, allowing both users and  
> maintainers to see what's what.

Would you please bring this subject to rubygems-devel mailing list?

http://rubyforge.org/mailman/listinfo/rubygems-developers

I believe you have a point, but both Eric Hodel (maintainer) and Tom
Copeland (RubyForge) can provide more details about current situation
than I can do.

In any case, no more bundling will be present in new One-Click
Installer, but different packages will be generated (more details to
come).

Regards,
--
Luis Lavena