microsoft / microsoft/winget-cli
Add support for .cab 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
Partially related to #684, but that thread's topic is much broader than this one's.
This would allow https://www.catalog.update.microsoft.com/Home.aspx to become a more viable source for new winget-pkgs packages. A fair few tech producers (I unfortunately don't have a chance this afternoon to look into which exact ones) and a few fringe cases on Microsoft Download Center (including https://www.microsoft.com/en-gb/download/details.aspx?id=102745) also make use of .cab files.
Proposed technical implementation details
Allow the use of .cab 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 by tracing how InstallerUrl values are validated and handled for .exe, .msi, .msix, .appx, .msixbundle, .appxbundle, and .zip. The work is done when .cab InstallerUrl values are accepted and supported consistently with those existing formats, with coverage for the new case.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100