microsoft / microsoft/winget-cli
[Feature Request] Local File Support for InstallerURL Property in Manifest File
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
I described the Feature here as an Issue:
https://github.com/microsoft/winget-cli/issues/4358
Desired are local relative / full Paths for the InstallerURL Property in Package Manifest File like:
./Microsoft Visual Studio Code_1.88.0_User_X64_inno_en-US.exe (relative to the same Directory as the manifest file)
and/or
D:/TEMP/tempdown/Microsoft Visual Studio Code_1.88.0_User_X64_inno_en-US.exe
and/or
file://D:/TEMP/tempdown/Microsoft Visual Studio Code_1.88.0_User_X64_inno_en-US.exe
If the Feature Request is ok and its no Issue you can close the Issue.
Thanks!
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 reading the related feature discussion in issue #4358 and the comments here, focusing on the supported semantics for InstallerURL in package manifests. Trace how manifests are parsed and how installer URLs are resolved, then define the expected behavior for relative paths, absolute paths, and file:// URLs. Done means the chosen local-path behavior is implemented with coverage for the supported forms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100