homebrew-cask

Commit Graph

Author	SHA1	Message	Date
Josh Hagins	8a2aaba17b	Don't explicitly exit with 0 after success Once Homebrew stops explicitly exiting with 0 after running our entry script, we should do the same.	2015-12-16 23:43:25 -05:00
Mike McQuaid	fdb4577be8	brew-cask: move to using tap cmd directory. This provides a few benefits: - faster `brew cask` execution times as another Ruby process is not needed. Cask can instead be loaded in-process with Homebrew. This will also make it easier to use some of Homebrew's core code and ease moving code from Cask into Homebrew core. - Users do not need to `brew upgrade` Cask any more: it's done automatically on any `brew update` or `git pull` of the Cask tap.	2015-12-09 19:32:49 +00:00

Author

SHA1

Message

Date

Josh Hagins

8a2aaba17b

Don't explicitly exit with 0 after success

Once Homebrew stops explicitly exiting with 0 after running our entry
script, we should do the same.

2015-12-16 23:43:25 -05:00

Mike McQuaid

fdb4577be8

brew-cask: move to using tap cmd directory.

This provides a few benefits:

- faster `brew cask` execution times as another Ruby process is not
  needed. Cask can instead be loaded in-process with Homebrew. This
  will also make it easier to use some of Homebrew's core code and
  ease moving code from Cask into Homebrew core.
- Users do not need to `brew upgrade` Cask any more: it's done
  automatically on any `brew update` or `git pull` of the Cask tap.

2015-12-09 19:32:49 +00:00

2 Commits