Most developers working on Mac will use homebrew to install packages. From the homebrew documentation on github:
"Our policy is that formulae in the core repository (Homebrew/homebrew) must be built from source. Binary-only formulae should go to Homebrew/homebrew-binary."
I imagine this is because it's safer to compile from source because anyone could put anything in a executable. However there isn't a great deal here in this homebrew-binary directory. In practice, for binaries on mac people generally use cask.
To install cask:
brew install caskroom/cask/brew-cask
Install binary applications with cask:
"Our policy is that formulae in the core repository (Homebrew/homebrew) must be built from source. Binary-only formulae should go to Homebrew/homebrew-binary."
I imagine this is because it's safer to compile from source because anyone could put anything in a executable. However there isn't a great deal here in this homebrew-binary directory. In practice, for binaries on mac people generally use cask.
To install cask:
brew install caskroom/cask/brew-cask
Install binary applications with cask:
brew cask install visualvm
brew cask install google-chrome
Cask is implemented as an external command in homebrew.
No comments:
Post a Comment