It's getting better.
John Leach over at Brightbox has a ppa with up-to-date binary ruby packages: http://blog.brightbox.co.uk/posts/next-generation-ruby-packa... https://launchpad.net/~brightbox/+archive/ruby-ng-experiment...
I'd suggest giving them a go, and mirroring them inside your infrastructure if they work for you.
It's very annoying that checkinstall doesn't Just Work for recent ruby builds. If it did, I'd suggest that every time.
> It get's really interesting once you use puppet to install an RVM ruby version.
Yeah, don't do that.
> Yeah, don't do that.
Why not? Puppet-RVM (https://github.com/blt04/puppet-rvm ) works very well. And puppet is basically a system documentation. Since it's clear what's installed on the machine.
Second, it implies you've got build tools installed on your production machines. That's bad for security.
Third, I've seen RVM screw up too much to trust it. It's got far too many moving parts, and so far I haven't found anything I need which it does that isn't done better by some other simpler tool.
This is why it's not realistic to expect to use the system ruby for development: that's not what it's there for.
It's also worth noting that the version of Ruby in current Debian Stable (which is 1.9.3-p194) will in all likelihood be deprecated by ruby-core 2 years before the next Debian Stable release. Again, this is fine for Debian, because they have taken on the responsibility of keeping working the user applications which rely on the system ruby.
If you're complaining about the system ruby being so out of date that you can't develop applications on it, you're doing it wrong. The system ruby isn't for you.
It get's really interesting once you use puppet to install an RVM ruby version. Which you then use to install $GENERIC_RUBY package (ie Gitlab) via Puppet.
I don't want to talk about the mess called "Puppet"...