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

WinGet "List" without hitting the network #4449

Open
denelon opened this issue May 6, 2024 · 2 comments
Open

WinGet "List" without hitting the network #4449

denelon opened this issue May 6, 2024 · 2 comments
Labels
Command-List Issue related to WinGet List Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@denelon
Copy link
Contributor

denelon commented May 6, 2024

Description of the new feature / enhancement

Sometimes I want to get an inventory of the devices and I don't want to incur the cost of the network traffic or performance hit to query the available versions, and or the sources where these packages are available.

This would likely be some kind of argument passed to the "list" command.

The scenario was proposed by an IT administrator looking to get an inventory of the installed packages and their versions.

Proposed technical implementation details

No response

@denelon denelon added Issue-Feature This is a feature request for the Windows Package Manager client. Command-List Issue related to WinGet List labels May 6, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage Issue need to be triaged and removed Needs-Triage Issue need to be triaged labels May 6, 2024
@jantari
Copy link

jantari commented May 15, 2024

Same thing for winget export please

@denelon
Copy link
Contributor Author

denelon commented May 16, 2024

WinGet export needs the correlation with package identifiers to succeed. I'm not sure that would work for an offline scenario. Even with WinGet list avoiding network traffic, the identifiers wouldn't be present, but it could show the display name, version, and some unique identifier from the system (package family name, product code, registry key, etc.). This version of list wouldn't be able to include a WinGet package identifier without first downloading the index for correlation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-List Issue related to WinGet List Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests

2 participants