Postmodern

Spoke with someone more knowledgeable of Debian Packaging. It shouldn't be necessary to split the `install` task. It's ok if dh_installdocs re-installs any documentation. `DESTDIR` stuff looks good.

Ah ha. It looks like I used the RedHat style of `DOC_DIR` (`name-version`). Yeah, let's make `DOC_DIR` configurable and default it to `PREFIX/share/doc/NAME`.

@jnv I believe just ensuring documentation is installed in the correct location. That and rebasing it against current master.

What's the purpose of these changes? I assume one can still execute the sub-command under dash, so long as chruby exports `PATH`, `GEM_HOME`, `GEM_PATH`, etc.

Ah I see. The purpose of running chruby within `$SHELL` is to support any shell specific configuration the user setup. You could export `SHELL` to ensure `chruby-exec` invokes bash instead...

What is the default shell of the user that runs this script?

@jrochkind random question, but why do you keep around older ruby versions?

FYI we are considering controlling `RUBIES` via a function, which can allow monkey patching, for 1.0.0. So expected something like the above example to become standard.

Perhaps we should have `test/setup` exit with -1 if it could not download the ruby?

I'm going to experiment with trying to move the ruby version/path variables into the Makefile, that way we can define an explicit dependency on `path/to/test/ruby-X.Y.Z`.