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
History subcommand #4421
Labels
Issue-Feature
This is a feature request for the Windows Package Manager client.
Comments
otto-liljalaakso-nt
added
the
Issue-Feature
This is a feature request for the Windows Package Manager client.
label
Apr 29, 2024
microsoft-github-policy-service
bot
added
the
Needs-Triage
Issue need to be triaged
label
Apr 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the new feature / enhancement
Some other package managers keep track of history of operations. For example, see History Command in dnf manual. Having similar functionality available in Winget would be very useful. In particular, winget packages very often have upgrade path bugs, and writing an accurate bug report would require knowledge of how the package was installed, and when.
winget history Troublesome.Package
would help a lot there.Proposed technical implementation details
I do not have very specific requirements for this. I think dnf's approach where every applied transaction is good. I think the following would be enough for the need I have:
(I am not sure if Winget does transactions, or just single package upgrades in sequence — if there are no transactions, then just logging individual operations in sequence would be enough.)
The text was updated successfully, but these errors were encountered: