microsoft / microsoft/winget-cli
Optimising package download bandwidth
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
Individual package downloads can consume significant bandwidth, especially in corporate environments with many users installing at a scheduled time. Is there a recommended approach for caching/optimising downloads?
Proposed technical implementation details
Package management systems like Intune have robust mechanisms for delivering content, eg Delivery Optimization and Microsoft Connected Cache. Could winget be configured to search a local path for pre-staged installer(s)?
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
The issue names no files, tests, or entry points. Start by tracing how winget downloads package installers and review how a local pre-staged path or download cache could be configured. Done would require a defined caching or local-path behavior that reduces repeated bandwidth use, along with documented configuration and validation.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100