Use Ruby apt package instead of compiling from source about roundsman HOT 3 OPEN

Sometimes it's critical to build exact patchlevel. And really, -p0 is way too old and have many bugs (for example, with yaml merging)

from roundsman.

1. There are PPAs (apt repositories) for more recent versions of Ruby, such as http://wiki.brightbox.co.uk/docs:ruby-ng, which (as of now) has the latest and greatest Ruby 1.9.3 p194.

2. For Ruby projects: Assuming your chef recipes are going to install RVM to make upgrading Ruby easier, and then build the specific version of Ruby that the project requires, it really makes no sense to build another version for Chef when we can just use the system-provided one. I'm fairly sure Chef is tested on common system rubies.

3. For non-Ruby projects: we care about the Ruby version even less.

from roundsman.

Fortunately, the installation method is completely configurable.

set :care_about_ruby_version, :false
set :ruby_dependencies, %w(build-essential)
set :ruby_install_script, "apt-get install -q -y ruby1.9.1 ruby1.9.1-dev"

(Ruby itself doesn't need build-essential, but it's required to compile Chef dependencies).

But even this is not the optimal approach!

Chef has official packages available for Debian/Ubuntu. It only makes sense to use them instead of mucking around with ruby-build, gem installs and such.

from roundsman.