[New Bug/Feature]: Package Dependency Scope/Arch Mismatch #3838
Labels
Issue-Bug
It either shouldn't be doing this or needs an investigation.
Issue-Feature
This is a feature request for the Windows Package Manager client.
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:
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?
elevationRequired
packages have?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.
The text was updated successfully, but these errors were encountered: