microsoft / microsoft/winget-cli
Configure export should mark packages needing elevation appropriately
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
When I run winget configure export --all -o config.winget and one or more packages require elevation to install, the configuration file should add the correct "elevationContext" to the configuration file so the single UAC elevation at the beginning of the configuration is sufficient.
I know some programs will still not necessarily behave the desired way like Git.Git which will check if the user installing the package is a local administrator to determine scope, so there will still be edge cases when this feature is implemented.
Proposed technical implementation details
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin at the WinGet CLI configure export --all -o config.winget command and trace how exported configuration entries are produced. Compare package elevation requirements with the emitted elevationContext, then verify that one initial UAC elevation covers applicable packages; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100