microsoft / microsoft/winget-cli
`--installer-type exe` filter should work with `nullsoft`, `inno` and `burn`
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
This is mostly for enhancing user experience. When I give --installer-type exe for winget (install|upgrade|download|show) command, then I would expect to get an EXE based installer (ending in .exe extension). Currently, the filter works if manifest specifies only InstallerType: exe. I would expect the filter to work with different variants of EXE installers i.e., inno, nullsoft, or burn.
If multiple EXE variants are found within the same manifest, then the CLI should throw an error and ask the user to disambiguate.
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
Start by tracing how the winget install, upgrade, download, and show commands apply the --installer-type filter. Check how exe, nullsoft, inno, and burn are represented and selected within a manifest. Done means --installer-type exe accepts those variants and reports an ambiguity error when multiple EXE variants match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100