Postmodern

@alyssais should these dependencies be added to any other rubies that compile?

@alyssais also, is this an issue that should be fixed in the Arch Docker image, or is it intentionally bare bones?

We could add `awk`, but `ruby-install` uses `grep` internally before it even gets to installing dependencies, so that wouldn't work. Also, `ruby-install` is not necessarily needed to install a ruby...

I thought about naming `--latest` as `--update`, but `ruby-install --update ruby` seemed kind of confusing; whereas `ruby-install --latest ruby` reads better. `--sync` was also considered. My assumption was a user...

I've added `-U,--update` in 9196cc4 and adjusted the wording in the README in 14375a02ff9287b77e877e94483ef00acf09f1dc.

This is a known issue with MRI. I'm guessing you're `$HOME` or the `src` directory is still on the old HDD?

Aforementioned upstream bug: https://bugs.ruby-lang.org/issues/9010 Confirmed that I can reproduce this with: ``` $ HOME="$PWD/fake home" ruby-install ruby 2.2.1 linking ruby gcc: error: home/.rubies/ruby-2.2.1/lib: No such file or directory gcc: error:...

We could remove the clean step entirely and just hope that `./configure` and the `Makefile` are smart enough to regenerate any pre-existing artifacts?

@judofyr could you do a quick test in your environment to whether `make clean` is the culprit? That forum post mentioned `make distclean` which is different. If `make clean` is...

I think we would need to add a separate function that only checked whether one (or maybe more?) dependencies were already installed? The function would need a similar `case/esac` statement...