Sorry for not being specific. I was just thinking about some of the Slicer users I know who are MDs. I am not sure they would appreciate using terminal and learning about brew and casks. I can’t imagine them running the steps you listed in “Steps to upgrade Slicer app (for users)” on the page lab page you referenced.
For the users like above, the package is the dmg file that they download from the Slicer web page.
I’m not a mac user, but this seems to be a very nice option for developers who use homebrew for installing applications.
Do you know if we can track number of downloads/installations/updates done through homebrew? If not, then we need to implement a more robust mechanism to measure application usage (e.g., check for updates at application startup and count these checks on the server side).
I completely agree. It is very nice to have this feature, I am glad @Fernando is working on this, and I appreciate it! All I am saying is that it will not replace the downloadable dmg packages for Mac for all of the Slicer users on Mac.
Andrey, I didn’t propose it as a replacement of the package but as an alternative for the process of installing and upgrading. I think most users (like the MDs) will be doing it the traditional way, but I also think that developers will appreciate this approach. Also, it’s very easy to maintain by the Kitware machines. I think @jcfr can confirm this.
Also, the package is downloaded and automatically mounted, installed and unmounted by brew.
While 4.7.0 and 26273 respectively correspond to the major.minor.patch version and the SVN revision (and I should be able to write a small script getting that info from either slicer.kitware.com or download.slicer.org). What is the value 676538 ?