WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
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:
Transaction date
Package IDs
Version numbers from
Version numbers to
Operation type: install, upgrade or remove
(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.)
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.Packagewould 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.)