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

Generally avoid latest as version #10437

Closed
Yann-R opened this issue Apr 5, 2015 · 1 comment
Closed

Generally avoid latest as version #10437

Yann-R opened this issue Apr 5, 2015 · 1 comment

Comments

@Yann-R
Copy link

Yann-R commented Apr 5, 2015

Hello,

Whilst I know that currently, homebrew-cask is not able to automatically manage updates of installed casks (and that people are actively thinking of how to implement it) I wonder if systematically avoid the use of :latest as version number in formulae wouldn't be a first "good practice".

In fact, I observed that `brew cask install```already-installed-formula`` is quite useful to get a new version when availaible:

  • you get a warning telling you it's already installed (if the version has not been updated)
  • or you download and install the new version (if updated)

So this is a way to easily maintain our installed software up-to-date.
But this nice behavior seems impossible if the formula updates keep always :latest as version number instead of the real software version number. Moreover, most of the time this version number really exists for the original software and it would be logical to write this original version number in the formula, even if the download link does not contain a version number.

Wouldn't it be a good idea to remove those :latest as often as possible?

@vitorgalvao
Copy link
Member

For some casks, this is downright impossible without having the cask break constantly. Those are the casks that have an unversioned url, such as zooom.

For all the others, yes, we’re currently shifting to remove :latest as often as possible.

This has all been discussed in #1021. See #1021 (comment) for a succinct conclusion.

@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

2 participants