The suggested and easiest way to install Homebrew is on the homepage.
The standard script installs Homebrew to
/usr/local so that
you don’t need sudo when you
brew install. It is a careful script; it can be run even if you have stuff
/usr/local already. It tells you exactly what it will do before
it does it too. And you have to confirm everything it will do before it starts.
xcode-select --install, developer.apple.com/downloads or Xcode 3
Because GitHub now only allows clients that support TLS 1.2 to access repositories over HTTPS, the Homebrew installer will use the GIT protocol when run on systems older than OS X Mavericks (10.9). This requires the availability of a
git binary, which can be provided by pre-installing the Command Line Tools or Xcode on Lion or Mountain Lion, or a prepackaged installer on Leopard or Snow Leopard. Homebrew will also require the Command Line Tools or Xcode in order to automatically compile and install a newer
git with support for TLS 1.2.
Also note that when installing on OS X Leopard (10.5), you need to bypass its outdated built-in certificates by adding
--insecure to the installation command’s list of
Just extract (or
git clone) Homebrew wherever you want. Just avoid:
/tmpsubdirectories because Homebrew gets upset.
/opt/localbecause build scripts get confused when Homebrew is there instead of Fink or MacPorts, respectively.
However do yourself a favor and install to
/usr/local. Some things may
not build when installed elsewhere. One of the reasons Homebrew just
works relative to the competition is because we recommend installing
/usr/local. Pick another prefix at your peril!
mkdir homebrew && curl -L https://github.com/Homebrew/brew/tarball/master | tar xz --strip 1 -C homebrew
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
Uninstallation is documented in the FAQ.
1 Not all formulae have CPU or OS requirements, but you can assume you will have trouble if you don’t conform. Also, you can find PowerPC and Tiger branches from other users in the fork network. See Interesting Taps and Forks.
3 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 Mac OS X. Sign up for free here.