Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Why I didn't upgrade Ruby 1.8.5 to 1.8.6
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Bob Ngu  
View profile  
 More options Jun 29 2008, 12:35 pm
From: Bob Ngu <bob_...@yahoo.com>
Date: Sun, 29 Jun 2008 09:35:31 -0700 (PDT)
Local: Sun, Jun 29 2008 12:35 pm
Subject: Why I didn't upgrade Ruby 1.8.5 to 1.8.6
Along with upgrading Rails to 2.1 (which I did successfully), I also
looked into upgrading Ruby from 1.8.5 to 1.8.6 (again on my Windows XP
machine), I came across this thread suggesting a workaround
-----------
    There’s no ruby update AFAIK. You can work around this by renaming
c:\ruby to something else, installing ruby, then overwrite C:\ruby\lib
\ruby\gems with the old version and call ‘gem update’ to fetch the new
versions.
-----------

After some investigation, I decided against it for the following
reasons.
   1. There is at least one new gem in Ruby 1.8.6, hpricot, that is
not in 1.8.5, so the above workaround would lose hpricot.
   2. c:\ruby\lib\ruby\gems (for the current Ruby 1.8.5) also include
all of Rails 1.2.3 gems. Although it seems like gem update would also
update Rails (presumably to 2.1), I am not comfortable that something
isn’t missing, could be unjustified paranoia but I am not taking any
chances.
   3. I use HTree which as it turns out is not installed as a gem, the
author didn’t bother to package it as a gem and instead uses Ruby 3rd
party extension / library mechanism instead meaning that it is
installed under c:\ruby\lib\ruby\site_ruby instead of c:\ruby\lib\ruby
\gems. The above workaround does not take this into account.

So I decided to stick with Ruby 1.8.5 since Rails 2.1 runs on it. If
anyone else has a more successful experience, please share.


    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2010 Google