microsoft / microsoft/winget-cli
[New Bug/Feature]: Package Dependency Scope/Arch Mismatch
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
Install is blocked by a dependency not having the same scope or architecture as requested by the main installer.
This can be seen in:
- https://github.com/microsoft/winget-pkgs/pull/121867
- https://github.com/microsoft/winget-pkgs/pull/121043
Unsure what the intended behavior here is, so unsure if feature or bug.
Proposed technical implementation details (optional)
There are many ways this could be resolved, and others might be better.
-
Possibly allow machine scope dependencies on user scope installs?
- Maybe with the same "expect a prompt" warning as
elevationRequiredpackages have?
- Maybe with the same "expect a prompt" warning as
-
Could also use a switch in WinGet to enable or disable this behavior on a per-install basis.
-
Failing could already be the best option, but there should be better communication about why.
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
No source files, tests, or entry points are named. Start by reviewing the linked winget-pkgs pull requests and reproducing the install failure to understand the scope and architecture mismatch; done means the intended behavior and user-facing handling are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100