microsoft / microsoft/winget-cli
Support UNC source
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
As an enterprise IT administrator I want to be able to have a UNC source so I don't have to stand up APIs or web services to provide a private repository to my users.
This may mean that the repository is simply a "manifests" folder, and the client needs to traverse the structure to pull in the information in order to support the "search" command.
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 package sources are handled for the search command, then determine where a UNC path and a manifests folder would fit in that flow. Done means the client can traverse the UNC repository and include its package information in search results without requiring an API or web service.
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
- 32/100