-
Notifications
You must be signed in to change notification settings - Fork 255
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
[BUG] Packages appear twice in Local Tab #117
Comments
This is completely my fault. I tried to be clever and just pull the list of packages by transversing the /lib/ folder. What is actually there and what chocolatey says is actually installed are two different things. |
this one makes me sad. |
I was so puzzled when I first discovered that. Apparently updates don't (or don't always) remove their previous version, so after updating my sysinternals twice I had three entries. @ferventcoder could probably explain why. I'm planning to swap back in the powershell clist call to get the local package list. |
Chocolatey doesn't by default remove the old package, which is a holdover from the ideas of ruby gems that you can have multiple versions of something installed. It is this concept that no other machine package manager holds, while it works for packages like ruby, it complicates everything else. We'll likely be cleaning up older packages as we go as we get closer to v1. |
For right now, I think what we should aim for is to simply display the latest version of an installed package. In the future, we could look to providing a details view that shows all the previously installed versions, but based on what @ferventcoder has just said, I think that would be a fruitless effort, if they are going to be removed in a future version. |
Fixed temporarily here. Forgot to reference the issue >_< |
For some packages, they appear in the Local Tab twice with different version numbers, as shown here:
Really only want to show a single entry, and once expanded, perhaps show all versions that are available locally.
The text was updated successfully, but these errors were encountered: