microsoft / microsoft/winget-cli
Negative Dependencies
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
Sometimes packages require things to not be installed / enabled. The current dependencies flow only accounts for enabling / installing, but doesn't have a way to cleanly terminate the install if windows features need to be disabled or other packages need to be uninstalled.
Currently, installers will just terminate with their error code, which could leave users wondering what the true issue is.
Proposed technical implementation details
No response
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 file, test, or entry point is named. Start by tracing the dependency flow and installer termination behavior in the C++ CLI, then identify how disabled Windows features or uninstalled packages should be represented. Done means negative dependencies terminate cleanly with an explanatory error instead of exposing only the installer exit code.
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