The difference between `brew` and `brew cask`

command linehomebrew

So, what is the difference between brew and brew cask?

I know that homebrew is a package management software. But what kind of software can I get there? Is it open source software and commercial software?

Best Answer

Homebrew

brew is the core command for the Homebrew project.

The missing package manager for OS X

Homebrew installs the stuff you need that Apple didn’t.

Homebrew typically deals with command line software. Most of the software is distributed under an open source licence. See the Formulas for a list of available installs.

brew prefers pre-compiled binaries but will compile from source in some cases.

Cask

brew cask is an extension to brew that allows management of graphical applications through the Cask project.

Homebrew Cask extends Homebrew and brings its elegance, simplicity, and speed to OS X applications and large binaries alike.

Cask deals with a mixture of software and licences. The software I work on is covered by a commercial licence and available via cask.

Cask offers a way to command line manage the installation of graphical applications.

See brew cask issue #7002 about the project's focus on predictability and how that affects the use of pre-compiled binaries or source.

Licensing

Availability through brew or cask does not imply any specific licence.

Related Solutions

The difference between .bash_profile and .bashrc

.bash_profile is executed for login shells, while .bashrc is executed for interactive non-login shells.

When you login (type username and password) via console, either sitting at the machine, or remotely via ssh: .bash_profile is executed to configure your shell before the initial command prompt.

But, if you’ve already logged into your machine and open a new terminal window (xterm) then .bashrc is executed before the window command prompt. .bashrc is also run when you start a new bash instance by typing /bin/bash in a terminal.

On OS X, Terminal by default runs a login shell every time, so this is a little different to most other systems, but you can configure that in the preferences.

MacOS – Check brew and brew-cask for valid package names

To get a list of invalid brew formulas:

#!/usr/bin/env bash
for formula in ${brews[@]}; do
    brew info ${formula} >/dev/null 2>&1 || echo ${formula}
done

To get a list of invalid casks:

#!/usr/bin/env bash
for cask in ${casks[@]}; do
    brew cask info ${cask} >/dev/null 2>&1 || echo ${cask}
done

(brews and casks are the arrays defined in your setup script.)