5 commits

Author	SHA1	Message	Date
phinze	c85ef168fc	require most commands to succeed; cleanup on install failure ... - add `run!` method which raises if command does not succeed - use `run!` when the command we are running must succeed for things to move forward. this should help produce clearer error messages in failure scenarios. - move caveats earlier in the install process so reports can be made about potential failures - remove the destination tree on cask install failure, so the cask will not be considered installed	2013-10-20 16:52:51 -05:00
Paul Hinze	17026b6e93	don't reinstall already installed casks ... thanks to @ccutrer for the catch; this implementation is based on his PR refs #233	2013-05-11 23:32:17 -05:00
phinze	fed2824c7f	add bona fide brew cask create command ... the create command opens up an editor with template to get started remove --create override flag from `brew cask edit` hopefully this will be more straightforward for contributors refs #306	2013-05-11 19:24:17 -05:00
phinze	ab57da07ea	add brew cask uninstall ... this delegates to homebrew's uninstall to get its work done. vanilla `brew uninstall` actually works, but this gives us a more consistent interface. as discussed in #47	2012-10-20 13:01:41 -05:00
phinze	b45974c224	support brew cask edit	2012-09-21 23:32:19 -05:00