### Untar anywhere and then symlink the `brew` command elsewhere
You can also install Homebrew into e.g.
`~/Developer` and then symlink the brew command into `/usr/local/bin`.
Everything will install into `~/Developer`, but your
brew command is still in the path. **NOTE** that Homebrew will still
need to create symlinks into `/usr/local` or nothing will
work! But the actual files are installed to
`~/Developer/Cellar`.
### Multiple installations
Create a Homebrew installation wherever you extract the tarball. Whichever brew command is called is where the packages will be installed. You can use this as you see fit, e.g. a system set of libs in `/usr/local` and tweaked formulae for development in `~/homebrew`.
<aname="2"><sup>2</sup></a> 10.7 or higher is recommended. 10.6 is supported on a
best-effort basis. For 10.4 and 10.5, see [Tigerbrew](https://github.com/mistydemeo/tigerbrew).
<aname="3"><sup>3</sup></a> Most formulae require a compiler. A handful require a full Xcode
installation. You can install Xcode, the CLT, or both; Homebrew
supports all three configurations. Downloading Xcode may require an Apple Developer account on older versions of OS X. Sign up for free [here](https://developer.apple.com/register/index.action).
<aname="4"><sup>4</sup></a> The one-liner installation method found on
[brew.sh](http://brew.sh) requires a Bourne-compatible shell (e.g.
bash or zsh). Notably, fish, tcsh and csh will not work.