From: Curt Hibbs <ml.chibbs@...>
Date: 2006-05-27T16:49:35+09:00
Subject: Re: ri broken?

------=_Part_1177_21869839.1148716172165
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 5/26/06, ara.t.howard@noaa.gov <ara.t.howard@noaa.gov> wrote:
>
> On Sat, 27 May 2006, James Britt wrote:
>
> > Ryan Leavengood wrote:
> >> On 5/26/06, James Britt <james_b@neurogami.com> wrote:
> >
> >> .. With our current solution we are being explicit that you're old rub=
y
> >> install will be uninstalled first, so at least you know what you are
> >> getting into.
> >>
> >>> A job for Rake or Reap or Rant ...
> >>
> >>
> >> To me that sounds like RubyGems could use some improvements...like
> >> maybe bulk installs, or a nice point and click GUI (click all the
> >> checkboxes for the gems you want.) In fact now that I've thought of
> >> this I'm surprised no one has coded that up.
> >>
> >
> > But it's not not just gems that would have to migrate, but all the libs
> > installed with setup.rb or install.rb or whatever was used.
>
> not to mention all binary gems would need re-compiled.


There's no guarantee that existing libs are compatible with new Ruby
releases. They might be, and they might not.

To be perfectly blunt, the one-click installer is now up to about 6,000
downloads a day, and anything that we can do to minimize support problems i=
s
a blessing.

Curt

------=_Part_1177_21869839.1148716172165--