homebrew-cask

I went ahead and added this to homebrew cask! Here's my PR[0]. Hopefully it will be merged soon. [0]: https://github.com/caskroom/homebrew-cask/pull/6591

I looked into adding one to homebrew-cask[0], but it isn't quite as easy as the rust nightly, because it doesn't use a pkg. It shouldn't be too hard though, to do it from that tar. [0]: https://github.com/caskroom/homebrew-cask

I think one of the things that the author forgot to mention is that you don't have to install these as `sudo` basically, homebrew does that already but with other things there no really need for it. As of the FOSS/Linux stuff you are seeing, these aren't random files, these are mac apps see: https://github.com/caskroom/homebrew-cask

Unfortunately there's still no proper "upgrade" command for cask, there's a lengthy discussion on how to deal with that on their issue tracker [0] though. For now you'll still have to rely on a workaround. Currently I'm using an alias to clear the old binary and download the new one. [1] [0] https://github.com/caskroom/homebrew-cask/issues/309 [1] https://blog.notmyhostna.me/make-calibre-updates-less-annoyi...

OSX has homebrew-cask [0, 1], which is built on homebrew to distribute binaries. I checked and a formula for calibre is present. [2] [0]: http://caskroom.io/ [1]: https://github.com/caskroom/homebrew-cask [2]: https://github.com/caskroom/homebrew-cask/blob/master/Casks/...

Additions: * lunchy: wrapper over launchctl, written in Ruby – https://github.com/mperham/lunchy * brew cask: "«To install, drag this icon...» no more", as they say – https://github.com/caskroom/homebrew-cask * have fun with "say" – https://github.com/andreis/different

Hey there! This is a valid concern, but I don't think it's all that different from using Homebrew. The community maintains the cask definitions, and all pull requests are reviewed via the project team. There's a checksum verification feature built in, though we're still figuring out how to reconcile that with un-versioned download URLs [1]. At the end of the day, when you use any package management software, you are implicitly trusting the team that maintains said software. Perhaps it would be better for us to do our best to force users to make that trust more explicit? It's an interesting question - any suggestions you have would be more than welcome - feel free to open an issue to discuss! :) [1] https://github.com/caskroom/homebrew-cask/issues/1021

I'm hoping someone could answer this for me. How do you trust the applications that `brew cask` installs? What is preventing `brew cask install firefox` from installing something malicious? When I download an application manually, I trust the site I'm on by virtue of being there and being savvy enough to know it's a legitimate site. But when you script it, you lose the ability to gauge see for yourself what you're downloading. I realize I could probably do: `brew cask info firefox`, find the ruby file it points to (https://github.com/caskroom/homebrew-cask/commits/master/Cas...), open that up, verify the link is trustworthy.. but I don't want to do that for every installation. And if it's valid now, what's to prevent it from changing in the future? How do you guys justify using cask?

Nice. Now add "brew cask" support (https://github.com/phinze/homebrew-cask basically brew for GUI apps) and I could see non-developers using it as well.

I don't think this synchronizes installations since the forumla[0] are overwritten with each update. If someone updates one of them the specific version you downloaded elsewhere will not be downloaded again. I definitely understand why homebrew works this way, but the logic for symlinking the applications is all in this extension[1] so this could easily be changed. I agree that symlinks is better for tools typical to homebrew but for this it's not like it symlinks your preference files so you're not actually cleaning up any junk if you uninstall the application through cask, it's the equivalent of just dragged it to the trash. Also the applications will still attempt to update so it's not managing versions that way either. [0]: https://github.com/phinze/homebrew-cask/tree/master/Casks [1]: https://github.com/phinze/homebrew-cask/blob/mast

There are a few things I don't like about this homebrew-cask. My biggest issue currently, now that the installation path can be specified as /Applications instead of ~/Applications[0], is that it makes a symbolic link from its install location to the Applications folder. Since the standard for GUI applications on OS X is to have some built in update system, I just want the applications to be copied to my install location and left alone. This means it would only automate the install process which I think would be better then managing their lifecycle. [0]: https://github.com/phinze/homebrew-cask/blob/master/USAGE.md...