Postmodern

Eh, maybe it might be better to print the list of supported rubies if the ruby name is unknown?

We could add debugging messages and a `--debug` option. We'd also need to identify the critical commands that need to be logged.

I plan on adding a `ruby-uninstall` command. It should `cd` back into the ruby's src dir and run `make uninstall` or `rake uninstall`, if available.

Curious whether this happens when compiling ruby-1.9.3-p551 manually?

@zenspider are there specific env variables that need to be passed thru? Preserving the whole environment with sudo is a potential security risk. `sudo --preserve-env=...` would be safer.

OK ok, I like @havenwood's idea of only allowing certain `HOMEBREW_*` env variables. We could use `--preserve-env=list` instead of `-E` to only pass in known `HOMEBREW_` environment variables and avoid...

It just occurred to me that using `sudo -E` or even `sudo --preserve-env=HOMEBREW_*,...` would not work _if_ you invoked `ruby-install` with `sudo` initially. The initial `sudo` would filter out any...

I am curious how most homebrew users set the `HOMEBREW_*` env variables? Is it explicitly with each command or is it set in `~/.bashrc`/`~/.zshrc`/`~/.profile`? We could try executing the `brew`...

I'm not sure a canonical one exists?

I want to keep additional env variables to a minimum. I've been meaning to write a plugin for rbenv but never got around to it. The only problem is that...