On Mon, Nov 23, 2009 at 1:23 PM, Gordon Thiesfeld <
gthie...@gmail.com> wrote:
>> I hope Curt Hibbs is reading thius. One of the commenters mentioned
>> the hassle some gems/projects on RF are going to have and he mentioned
>> various Win32 stuff along with the OneClick Installer. RF isn't going
>> anywhere soon and I don't think OCI is considered a gem. But maybe
>> Curt should be aware of the switch?
>>
>
> The commenter you're talking about is probably Luis Lavena. He took
> over as maintainer of the OneClick installer - now known as
> RubyInstaller[1] - in December of 2007[2].
>
>>
Luis commented on the Google group for RubyInstaller (The 5-click
Installer :) that gemcutter works with it, but he hasn't tested
jeweler. (if it doesn't shell out to *nix commands, it shuld be fine).
So he is aware of the move.
Gem's must from now on be "pushed" to gemvutter, if hosted on RF:
I'm copying this email for folks who might have gems on RubyForge:
Date: Sat, 21 Nov 2009 22:15:15 -0500 (EST)
From:
nor...@rubyforge.org
To:
m...@mydomain.com
Subject: [RubyForge] Gem index has been shut down
Hello -
You’re receiving this email because you’re a RubyForge project admin
and a recent change robably affects you.
A few days ago we repointed
gems.rubyforge.org to the
gemcutter.org
box. This means that Nick Quaranto’s excellent gemcutter app is now
indexing and serving all the gems - so rather than having two gem
indexes, we now have one. As a consequence of this, when you release
files to RubyForge you will probably also want to do a “gem push” to
get them onto gemcutter and into the main gem index.
Note that you can continue to release gems (and other files) at
RubyForge; it’s just that gems won’t utomatically make it into the
main gem index.
Yours,
The RubyForge support team
http://rubyforge.org/projects/support/