Re: [Homebrew/homebrew-cask] Update screen from 1.2.6 to 1.2.7 (#84292)

From: notifications@github.com
Domain: IP info github.com
MX-server: IP info out-16.smtp.github.com
Size: 3375 Bytes
Create: 2020-06-20
Update: 2020-06-20
Score: 0
Safe: Yes

Outbound domains: github.com |

@jsherwani Thanks for the ping! Sorry for the delay in getting back to you. HBC itself has a appcast system that deals with updates universally.

Is homebrew responsible just for downloading the app, and then it functions just as though the user downloaded the app themselves from our website?

That's the idea. But upon uninstall, we maybe cleanout files/folders better than just dragging the .app into the trash.

I couldn't find any documentation on this, other than: #72166 (files), which seemed somewhat eerie — is it no longer considered generally safe for apps to update themselves? If so, how do apps that have update mechanisms inter-operate with homebrew?

I think it's still generally safe. I think the reason for removal was because people were thinking that adding auto-update to everything was okay when in many situations it isn't. If an app isn't set up properly to auto-update there could be some data-loss on the user's side, because we'll essentially uninstall and reinstall the latest version.

If so, how do apps that have update mechanisms inter-operate with homebrew?

I don't think we have mechanisms that 'inter-operate', but rather it's more about the brew cask upgrade process.

I hope that answers all your questions. Feel free to reply, if have any more or I didn't properly address anything.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Want to protect your real email from messages like this? Use TempM email and be more secure on the internet.