You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Clarify the values allowed in the ElevationRequirement field #3286
After reading #1284 and look into the spec I am not able to understand the elevatesSelf value purpose.
The "elevatesSelf" value is being set for installers which do need admin privileges (eg. Python.Python.3.11), this is counter intuitive to the "scope: User" .
elevationRequired - is clear: should be filtered out on scope User
elevationProhibited - is clear: should be used with system/admin level privileges, should be filtered out on scope Machine
ElevationRequirement and Scope are only loosely related.
elevationRequired - Must be run from a shell that is running in an administrative context (e.g - Admin user using powershell/terminal/cmd with "Run as Administrator")
elevationProhibited - Must be run from a shell that is not running in an administrative context
elevatesSelf - If called from a non-administrative context, will request elevation. If called from an administrative context, may or may not request elevation.
Some applications require elevation to install in the user scope, others do not. Some will install to the machine scope without elevation, others will not
Activity
Trenly commentedon May 30, 2023
ElevationRequirement and Scope are only loosely related.
Some applications require elevation to install in the user scope, others do not. Some will install to the machine scope without elevation, others will not
denelon commentedon May 30, 2023
Looks like I didn't add the enumeration to:
https://github.com/microsoft/winget-pkgs/blob/master/doc/manifest/schema/1.4.0/installer.md