microsoft / microsoft/winget-cli
Remove support for Neutral architecture
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
Related to #1980
This would be a breaking change
With tools for creating multimanifests being well established, the ability to add multiple installer nodes is fairly trivial. As the client becomes smarter in terms of determining supported architectures and mapping packages to a users preferred or required architecture, the removal of neutral would force package metadata to be more complete.
Proposed technical implementation details
In the case of a neutral installer, an installer node for each architecture could be used instead.
Alternatively, Architecture could be changed to an array type. This (personally) would make the most sense, as it would align with the concept of Supported Architectures and UnsupportedArchitectures (#993)
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 architecture and neutral-installer handling described here, then read related issues #1980 and #993. Compare the proposed per-architecture installer nodes with changing Architecture to an array, and define the breaking-change scope and validation needed before implementation.
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
- Mostly clear
- Newbie friendliness
- 25/100