Important December update: Homebrew-Cask will now be kept up to date together with Homebrew (see #15381 for details). If you haven’t yet, run brew uninstall --force brew-cask; brew update to switch to the new system.
Important: At some point in the future Homebrew-cask will change its behaviour from linking apps to moving them. See issue #13201 for details.
“To install, drag this icon…” no more!
Homebrew-Cask extends Homebrew and brings its elegance, simplicity, and speed to the installation and management of GUI Mac applications such as Google Chrome and Adium.
We do this by providing a friendly homebrew-style CLI workflow for the administration of Mac applications distributed as binaries.
It’s implemented as a homebrew external command called cask.
To start using Homebrew-Cask, you just need Homebrew installed.
$ brew cask install google-chrome
=> Downloading https://dl.google.com/chrome/mac/stable/GGRO/googlechrome.dmg
=> Success! google-chrome installed to /opt/homebrew-cask/Caskroom/google-chrome/stable-channel
=> Linking Google Chrome.app to /Users/phinze/Applications/Google Chrome.appAnd there we have it. Google Chrome installed with a few quick commands: no clicking, no dragging, no dropping.
$ open ~/Applications/"Google Chrome.app"- Find basic documentation on using homebrew-cask in USAGE.md
- Want to contribute a Cask? Awesome! See CONTRIBUTING.md
- Want to hack on our code? Also awesome! See hacking.md
- More project-related details and discussion are available in FAQ.md and CASK_LANGUAGE_REFERENCE.md
We’re really rather friendly! Here are the best places to talk about the project:
- Start an issue on GitHub using one of these templates:
- Join us on IRC, we’re at
#homebrew-caskon Freenode
We still have bugs — and we are busy fixing them! If you have a problem, don’t be shy about reporting it on our GitHub issues page. Always search for your issue before posting a new one.
When reporting bugs, remember that homebrew-cask is an independent project from Homebrew. Do your best to direct bug reports to the appropriate project. If your command-line started with brew cask, bring the bug to us first!
Before reporting a bug, make sure you have the latest versions of homebrew, homebrew-cask, and all Taps by running the following command:
$ brew update; brew cleanup; brew cask cleanupIn addition, if you haven’t yet, run the following once to switch to the new system:
$ brew uninstall --force brew-cask; brew updateFinally, if it's been a while since you last updated Homebrew-Cask, you may still have the old phinze/cask tap installed. Run the following to clean up, then try your command again:
$ brew untap phinze/cask; brew untap caskroom/cask; brew updateIf the issue persists, please run the problematic command with the --verbose flag and post its and brew cask doctor’s outputs in distinct fenced code blocks.
Code is under the BSD 2 Clause (NetBSD) license