rmc-spock | ROSE meta config with Spock installation management

RMC/Spock is intentionally easy to install into a ".spock" subdirectory of the user’s home. The entire procedure is:. The bootstrap.sh script has command-line options to control which versions of dependencies to use and whether it has permission to download their source code from the Internet if it can’t find the source code locally. RMC/Spock can be safely installed in ~/.spock even if the home directory is NFS-mounted on different architectures. Each host will have its own private areas under various architecture-dependent parts of the ~/.spock tree. TODO: Describe command-line options needed by various Linux distributions. E.g., RHEL 6 has an old C++ compiler that can’t handle some of the more modern dependencies. TODO: Describe how to install RMC/Spock on a machine with no Internet connection.
Intel compilers are a little strange because they require modifications to your shell environment before they can be used, and these modifications are more involved than setting a couple environment variables to easily determined values. This environmental pollution also makes it difficult to use more than one version of Intel compiler in the same shell session. RMC/Spock tries to alleviate some of this pain by enclosing the Intel compiler commands (found under /usr/apps/intel) in version-specific wrapper scripts with names like icpc-16.0.3 and placing them in your ~/bin directory. Tip: Now would be a good time to restart your login shell if you polluted the environment by sourcing any Intel configuration scripts. Running exec bash will probably not be sufficient! Also note that "rmc" is really only well tested in Bash shells, although it should work in others.