Hot answers tagged homebrew
Homebrew on its own acts like a command-line App Store. It's safe, if you know what you're downloading. If you are concerned about downloading hijacked binaries, verify the SHA/SHA1 sum of the binary you've downloaded against the SHA/SHA1 sum published by the developer, usually on their webpage. Personally, I've never had any bad experiences with Homebrew. ...
The problem here is just simply that brew is detecting an old version of Xcode. If it was objecting to the version of the command line tools that you have installed you'd be getting a different error message. A newer Command Line Tools release is available. Update them from Software Update in the App Store. You can see the actual code here yourself. The ...
The command is supposed to move the tmux process from a newly created bootstrap context under the root, to the user's login bootstrap context. To explain that in slightly more common terms: macOS (formerly OS X) is built with a Mach-kernel at the lowest layer. Programs executing at this layer are called tasks. On top of the Mach-kernel is the BSD ...
Update: Current stable version (.67) of putty can't be build with gtk+2 support on OS X using homebrew. This is a know issue #40951. It seems you can install from HEAD version (brew install --HEAD --with-gtk+3 putty) and for me that is also broken. brew install putty by default installs from a pre-built bottle. The pre-built bottle for putty doesn't include ...
You should have a look at brew bundle, which installs as a subcommand of brew. It can install and update packages, taps, and casks specified in a Brewfile. You can also dump your current Homebrew environment into a new Brewfile or uninstall everything not listed.
You have to add /usr/local/sbin to your path. It was installed to /usr/local/sbin but that directory is not in your $PATH by default. Add a line like this to your ~/.bashrc or equivalent: export PATH=/usr/local/sbin:$PATH
Only top voted, non community-wiki answers of a minimum length are eligible