[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Ruby 1.9.1 and Rubygems

Michael Morin

2/1/2009 5:20:00 PM

Wanting to play with Ruby 1.9.1, I uninstalled (via apt) all my Ruby
packages, downloaded the Ruby 1.9.1 source code and installed with
/configure, make, then make install. At this point, Ruby works fine,
as do the irb, ri, etc commands. Next up, install Rubygems 1.3.1.
Download the source code, extract, and run ruby setup.rb. During the
install, it overwrites /usr/local/bin/ruby, breaking the Ruby
installation.

Why is Rubygems writing over /usr/local/bin/ruby?

I'm running Ubuntu 8.10, and I've uninstalled all Ruby-related
packages prior to doing this.

4 Answers

Codeblogger

2/1/2009 6:14:00 PM

0

[Note: parts of this message were removed to make it a legal post.]

Hello Michael,

Ruby 1.9.1 ships with built-in Rubygems. You do not need to install
Rubygems separately.

Regards
Nicolai

David Palm

2/1/2009 6:32:00 PM

0

> Ruby 1.9.1 ships with built-in Rubygems. You do not need to install
> Rubygems separately.

Right, but the question still stands: why on earth is the rubygems installer script attempting something so disruptive?

Did the OP file a bug to the rubygems devs?

>
> Regards
> Nicolai

Michael Morin

2/1/2009 6:39:00 PM

0

On Sun, Feb 1, 2009 at 1:13 PM, Codeblogger <codeblogger@gmail.com> wrote:
> Hello Michael,
>
> Ruby 1.9.1 ships with built-in Rubygems. You do not need to install
> Rubygems separately.
>
> Regards
> Nicolai

Wow... I didn't realize that at all! Has Rubygems been merged with
Ruby? How will updates of Rubygems be performed in the future? Is
the version of Rubygems now tied to the version of Ruby?

Michael Morin

2/1/2009 6:45:00 PM

0

On Sun, Feb 1, 2009 at 1:31 PM, David Palm <dvdplm@gmail.com> wrote:
> Right, but the question still stands: why on earth is the rubygems installer script attempting something so disruptive?
>
> Did the OP file a bug to the rubygems devs?

I have now.