microsoft / microsoft/winget-cli
Add support for .msu files as InstallerUrl-s in manifests.
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
This would allow https://www.catalog.update.microsoft.com/Home.aspx to become a more viable source for new winget-pkgs packages.
A handful of cases on Microsoft Download Center also make use of .msu files, including https://www.microsoft.com/en-gb/download/details.aspx?id=48231
Proposed technical implementation details
Allow the use of .msu files in InstallerUrl-s, in much the same way as what is the case at the time of writing with .exe/.msi/.msix/.appx/.msixbundle/.appxbundle/.zip.
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 in the WinGet CLI code that validates or processes InstallerUrl values for the existing .exe, .msi, .msix, .appx, .msixbundle, .appxbundle, and .zip extensions. Trace how those extensions are accepted and handled, then determine the corresponding validation and verification needed for .msu URLs. Done means manifests using .msu InstallerUrl values are accepted without regressing existing installer types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100