No, I don't see why you would do that. The best solution would be to
build with ./configure --program-suffix=*extension you tend to build
with with, for example, 1.9.1* This is the best solution, let ruby do
the work for you, rather then bypass what ruby has setup for you and try
to hack on it
Okay, but there is a serious problem with the current installation. It
needs to be fixed, if you want to try to patch rbconfig.rb then that is
fine but that is a dirty hack IMO. I don't see why --program-suffix=
would not work, but maybe try to address that problem? At the moment,
rubygems, mkmf,
Public bug reported:
Binary package hint: ruby1.9.1
The ruby 1.9.1 package made available in the karmic repository should
have been built ruby with --program-suffix=1.9.1 if it is going to
install ruby as ruby1.9.1. It doesn't do that however, and if, like me,
you have 1.8.7 installed as
Sorry, I didn't explain myself clearly in the initial bug report.
The ruby 1.9.1 package made available in the karmic repository should have been
built with --program-suffix=1.9.1 if the binary is going to be installed as
'/usr/bin/ruby1.9.1' but it fails to do so.
Possible problems could
