Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add some description of updating to the FAQ / Usage #403

Closed
lucas-clemente opened this issue May 31, 2013 · 8 comments
Closed

Add some description of updating to the FAQ / Usage #403

lucas-clemente opened this issue May 31, 2013 · 8 comments

Comments

@lucas-clemente
Copy link

I just found cask and am curious about your idea of handling app updates. Should I just normally use the app's update feature or wait for a cask update? Does it matter at all? ;)

I think a paragraph describing this should be added to the FAQ or maybe Usage, since I think many users might have that question.

@vitorgalvao
Copy link
Member

No, it doesn't really matter. Just from the way apps check for updates, it's more likely they’ll warn you before the cask gets updated anyway — I’d guess a lot of contributions come from people who got the app update warning a little before. The syntax is not really definitive yet, and that also causes some issues with upgrading, currently.

As far as I know, you’re the first one to raise that issue (which doesn’t mean, naturally, you’re the only one thinking it), but I don’t really think such a note is necessary. The system is versatile enough that you can do it however you’d like without a problem (except for the aforementioned case, that is being looked into).

@jonashaag
Copy link
Contributor

I just started using Cask and wondered about this too. Some hint in the README (even just a link to this bug) might be very helpful...

@saulshanabrook
Copy link
Contributor

Chiming in here, a note would be helpful to me as well.

@saulshanabrook
Copy link
Contributor

Or maybe considering issues with brew cask upgrade (#309), letting the app do it would be best

@Peeja
Copy link
Contributor

Peeja commented Jan 12, 2014

Here's an awkward case: TextMate 2 currently tells you when the version is old (and won't let you run versions if they're really old), but instructs you to download the latest version from the website. Because it's a "latest" version cask, there's no way to upgrade it with brew-cask. I can't even uninstall/reinstall, because it caches the download.

What's the right way to do this?

@Peeja
Copy link
Contributor

Peeja commented Jan 12, 2014

Hmm, I think I misunderstood. TM2 still has Sparkle, but it also has code which makes the app stop launching once it gets too old. That system has a warning when it gets closer to the cut off date, which has started to fire. But Sparkle claims I've got the latest version. I guess I just need to wait for a new version to be released.

@vitorgalvao
Copy link
Member

Regarding

Because it's a "latest" version cask, there's no way to upgrade it with brew-cask. I can't even uninstall/reinstall, because it caches the download.

Currently the best way to achieve this is to clear homebrew’s cache. brew cleanup --force -s && rm -rf $(brew --cache)' && brew cask uninstall textmate && brew cask install textmate

@phinze
Copy link
Contributor

phinze commented Jan 28, 2015

Our FAQ has several notes about updating. 🙆‍♀️

@phinze phinze closed this as completed Jan 28, 2015
@miccal miccal removed the documentation Issue regarding documentation. label Dec 23, 2016
@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants