Postmodern

The tests depend on knowing a specific version. Usually, [rvm-binary](https://github.com/rvm/rvm-binary) has decent coverage for recent ruby versions. If you're platform isn't supported, open an issue with them and they'll look...

`test/opt/rubies` is only created by the `test/setup` script, which is ran before the test suite. `test/` should be omitted from any package. I'd love to host the debian package files...

Sounds reasonable to search `$RUBIES` in reverse order.

That is definitely not right. It appears the fuzzy matching is matching the 2.**2.0** part.

@indirect checkout the [sequential_version_matching](https://github.com/postmodern/chruby/tree/sequential_version_matching) branch.

Maybe this could be a separate command that just does: ``` for ruby in "${RUBIES[@]}"; do chruby_use "$ruby" command here chruby_reset done ```

We could potentially add a separate file that appends Chef's Ruby to `$RUBIES`. I'm not sure how we could handle custom `GEM_ROOT`, `GEM_HOME` without fundamentally breaking chruby. Also, why do...

Correct. It would force users to explicitly invoke chruby-exec within a shell. This would be one way to prevent users from invoking chruby-exec under the dash shell. Of course, maybe...

chruby will not add `~/.gem/...` to `$GEM_PATH` when you are root. The idea being, if you are installing gems as root, you probably want to install them in the rubies...

Perhaps you could do something like `chruby-exec 2.1.2 -- sudo -E ...`. Although, it appears `sudo -E` is still clobbering `$PATH`.