Yes, that's exactly my point. The devs and admins at my company got together, decided what ruby version we were going to use, and stuck with that. It's not always going to be the same version, and at some point, we may decide to upgrade. But we want to do that on our schedule, and decide which version, not have a package maintainer decide for us. I'll keep my system fairly up to date, particularly with X and my window manager, but freeze the specific version of Ruby we're using in production. The server, though, only has security fixes installed, no other updates.
