microsoft / microsoft/winget-cli
Handle opposing elevation requirements for packages with 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
Some packages may have opposing elevation requirements for their dependencies.
Example:
Package foo depends on package bar.
Package foo requires elevation.
Package bar prohibits elevation.
-or vice-versa-
WinGet may need to simply inform the user so they can perform installs in the appropriate order or handle the elevation requests and manage the installation of the package and its dependency in a single flow without requiring a second install command.
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 files or tests are identified in the issue. Start at the winget CLI's dependency installation and elevation handling, then determine whether conflicting requirements should be reported for ordered installs or handled in one flow; done requires an agreed behavior and corresponding implementation and tests.
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