-
Notifications
You must be signed in to change notification settings - Fork 2
Installation on Linux
- curl
Just extract 4 (or git clone) Homebrew wherever you want. Just avoid:
- Directories with spaces in them because build scripts are dumb and can’t handle spaces.
The mac package recommends /usr/local. This probably isn’t advised on linux at this point – it is very experimental, and if you have root-level access you probably have a system package manager that is much more feature-complete!
4 Here’s a one-liner:
mkdir homebrew && curl -L https://github.com/ndevenish/homebrew/tarball/master | tar xz --strip 1 -C homebrew
Possibly, this is untested for Linux at the moment (though no obvious reason it shouldn’t work):
You can also install Homebrew into e.g. ~/Developer (or ~/.homebrew) 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.
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.
Let’s say you are developing an app that must distribute Taglib. Add Homebrew as a git submodule for your project and then make Xcode $PROJECT_ROOT/homebrew/bin/brew install taglib as part of the build process. This way you can easily build Taglib, tweak its build options as you like (brew edit taglib) and let the Homebrew community worry about keeping Taglib up to date for you.
If you use Homebrew at your company, you probably have your own fork with modifications relevant to your coworkers. Fortunately it is very easy to make Homebrew use a company fork rather than mxcl’s. Just change the origin remote of the git clone and Homebrew will continue to use that origin instead of the normal one. It is then up to you to update your fork as often as you see fit so that updates propagate. Feel free to fork the installation script to make it install your fork by default.
Since you shouldn’t be installing in system locations at the moment, you can probably just remove the whole folder.