What I expected: Ruby should install in /usr/bin and /usr/lib where the
previous ruby installation already is.
What happened: Ruby installed in /usr/local
What I did:
download ruby1.9-p243
unpack
./configure
make
sudo make install
Can someone help me to get this installed over the current ruby1.9-p129
installation which alread is at /usr/bin so I can keep all my already
installed gems.
Ray
Ubuntu 9.04
--
Posted via http://www.ruby-forum.com/.
I guess you should use
./configure --prefix=/usr
instead of simply
./configure
I hope this helps
Stefano
On Monday 31 August 2009, Rainer Kuhn wrote:
>What I expected: Ruby should install in /usr/bin and /usr/lib where the
>previous ruby installation already is.
>
>What happened: Ruby installed in /usr/local
>
>What I did:
>download ruby1.9-p243
>unpack
>./configure
>make
>sudo make install
>
>
>Can someone help me to get this installed over the current ruby1.9-p129
>installation which alread is at /usr/bin so I can keep all my already
>installed gems.
>
>Ray
>
>Ubuntu 9.04
>
Rainer Kuhn wrote:
What I expected: Ruby should install in /usr/bin and /usr/lib where the
previous ruby installation already is.What happened: Ruby installed in /usr/local
What I did:
download ruby1.9-p243
unpack
/configure
make
sudo make installCan someone help me to get this installed over the current ruby1.9-p129
installation which alread is at /usr/bin so I can keep all my already
installed gems.Ray
Ubuntu 9.04
Hi, I know this is an old thread, but being as how I have been using
source ruby for over two years now on Ubuntu, I will give a little
perspective, hopefully help someone out. Plus I just read the message.
I take it you installed ruby from the Ubuntu repository. That is fine,
but if you are going to switch to the source of ruby, you have to
uninstall the packages, and all that that implies for your gems, I would
suggest saving a list of the gems you have in a text file (gemlist.txt)
in the example) and running something like $ruby -e
'File.open("./gemlist.txt", "r").each {|g| `sudo gem install #{g}`}'
from the command line after you install new ruby from source.
Also, when you build ruby from source you need to "./configure
- --enable-shared" in Ubuntu to get it to play nice with some things.
Also, this automagically installs a new gem command, irb command, and
rdoc(as of ruby 1.9).
The reason why built-from-source ruby lives in /usr/local is because
Ubuntu 'owns' the files in /usr/bin and /usr/lib. When Ubuntu updates
packages, these packages change. You 'own' the files in /usr/local/*,
so you are responsible for making sure they stay up to date, Ubuntu does
not change them. The downside is that if you are building ruby from
source, you can't use the packages for ruby in Ubuntu. That's ok, most
of what you need comes automatically when you build the code from source.
hope this helped, a year too late perhaps!
G Brandon Hoyt
I couldn't agree more! It is a very bad idea to try to install over
those versions provided by the package manager. This is definitively
calling for trouble. It's easier to stick with the installation in
/usr/local and adjust either shebang in scripts or create a few
symlinks in /usr - although I would be cautious with that already.
Alternative: get a package from another source, e.g. 1.9.1.378-1:
http://packages.debian.org/squeeze/ruby1.9.1
http://packages.debian.org/sid/ruby1.9.1
or live with a tad older version 1.9.1.243-2:
http://packages.ubuntu.com/de/karmic/ruby1.9.1-full
Kind regards
robert
2010/3/10 G Brandon Hoyt <qrprat77@gmail.com>:
The reason why built-from-source ruby lives in /usr/local is because
Ubuntu 'owns' the files in /usr/bin and /usr/lib. When Ubuntu updates
packages, these packages change. You 'own' the files in /usr/local/*,
so you are responsible for making sure they stay up to date, Ubuntu does
not change them. The downside is that if you are building ruby from
source, you can't use the packages for ruby in Ubuntu. That's ok, most
of what you need comes automatically when you build the code from source.
--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/
Or just use Ruby Version Manager -- RVM
http://rvm.beginrescueend.com/
http://rvm.beginrescueend.com/rvm/install/
On Mar 10, 11:56 am, Robert Klemme <shortcut...@googlemail.com> wrote:
2010/3/10 G Brandon Hoyt <qrpra...@gmail.com>:
> The reason why built-from-source ruby lives in /usr/local is because
> Ubuntu 'owns' the files in /usr/bin and /usr/lib. When Ubuntu updates
> packages, these packages change. You 'own' the files in /usr/local/*,
> so you are responsible for making sure they stay up to date, Ubuntu does
> not change them. The downside is that if you are building ruby from
> source, you can't use the packages for ruby in Ubuntu. That's ok, most
> of what you need comes automatically when you build the code from source.I couldn't agree more! It is a very bad idea to try to install over
those versions provided by the package manager. This is definitively
calling for trouble. It's easier to stick with the installation in
/usr/local and adjust either shebang in scripts or create a few
symlinks in /usr - although I would be cautious with that already.Alternative: get a package from another source, e.g. 1.9.1.378-1:http://packages.debian.org/squeeze/ruby1.9.1http://packages.debian.org/sid/ruby1.9.1
or live with a tad older version 1.9.1.243-2:Ubuntu – Error
Kind regards
robert
--
remember.guy do |as, often| as.you_can - without endhttp://blog.rubybestpractices.com/