microsoft / microsoft/winget-cli
Two suggestions for a 2.0 release
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
Hello!
I noticed @denelon is asking for ideas that might justify a version bump to 2.0.
I hope the following two suggestions haven't been discussed and dismisses or approved yet, at least I could not find anything.
- Implement aliasses for existing store apps. Instead of letting users search for a cryptic ID and then use this in winget
- Change policy to allow certain selected installers to be downloaded from individually approved "foreign" sources.
Proposed technical implementation details
-
Expland the current manifest-scheme with fields that a "normal" winget-manifest can point to a store app (ID or whatever) and thus enable winget to handle it like any other programme.
-
This would require a policy change. I have tried to start a discussion without much feedback here: https://github.com/microsoft/winget-pkgs/discussions/97158
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 reviewing the current manifest scheme and the policy governing installer sources, then read the linked winget-pkgs discussion for existing context. The work would need agreed requirements and acceptance criteria for both store-app aliases and individually approved foreign sources before implementation could be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100