-
-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Handling of cask versions #7725
Comments
We’re aware and tracking these issues in #2988 and others. The logic to handle those correctly hasn’t been implemented yet. |
Okay, I was just afraid I was missing something. Is there a task list somewhere for this? I'm happy to help. |
@L2G You can take a look at issues tagged “roadmap” for clear lists on what the next steps on what still needs to be done are. |
@vitorgalvao Cool, thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are a couple of things in the handling of cask versions that I'm not seeing even though I'm expecting to see them.
First,
brew cask info
shows only the latest version of a cask, even if an older version has been installed and not yet removed.Second (and perhaps related), when a cask is installed and then a newer version appears,
brew cask info
shows that no version is installed at all, even ifbrew cask ls
shows that the cask is installed.Are these bugs or am I just not understanding how cask versions are supposed to work?
The text was updated successfully, but these errors were encountered: