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

[BUG] Packages appear twice in Local Tab #117

Closed
gep13 opened this issue Feb 20, 2014 · 6 comments
Closed

[BUG] Packages appear twice in Local Tab #117

gep13 opened this issue Feb 20, 2014 · 6 comments
Labels
Bug Issues where something has happened which was not expected or intended TaskItem Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Feb 20, 2014

For some packages, they appear in the Local Tab twice with different version numbers, as shown here:

image

Really only want to show a single entry, and once expanded, perhaps show all versions that are available locally.

@gep13 gep13 added this to the 0.12 milestone Feb 20, 2014
@gep13 gep13 added bug labels Feb 20, 2014
@RichiCoder1
Copy link
Contributor

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.

@rismoney
Copy link

What is actually there and what chocolatey says is actually installed are two different things.

this one makes me sad.
anywho- kudos to you - this has really come along awesomely!

@RichiCoder1
Copy link
Contributor

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.

@ferventcoder
Copy link
Member

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.

@gep13
Copy link
Member Author

gep13 commented Feb 21, 2014

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.

@RichiCoder1
Copy link
Contributor

Fixed temporarily here. Forgot to reference the issue >_<

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues where something has happened which was not expected or intended TaskItem Non-bug, non-feature related things. Could be refactoring. Sometimes non-code related things.
Projects
None yet
Development

No branches or pull requests

4 participants