-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expected return codes #1278
Labels
Area-Manifest
This may require a change to the manifest
Issue-Feature
This is a feature request for the Windows Package Manager client.
Milestone
Comments
denelon
added
Issue-Feature
This is a feature request for the Windows Package Manager client.
Area-Manifest
This may require a change to the manifest
labels
Jul 13, 2021
This will not be supported fully until the validation pipelines accept the 1.1 schema. winget-cli/schemas/JSON/manifests/v1.1.0/manifest.installer.1.1.0.json Lines 154 to 186 in 5a97e26
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area-Manifest
This may require a change to the manifest
Issue-Feature
This is a feature request for the Windows Package Manager client.
Description of the new feature/enhancement
Some .exe installers provide return error codes for known reasons on install. These aren't exactly the same as "SuccessCodes" because the install didn't complete, but they aren't necessarily catastrophic failures either.
We would like to be able to have standard known error messages that can be easily understood and localized for these installers.
Proposed technical implementation details (optional)
The Windows Package Manager would have an enumeration of responses to be localized for mapping to specific return codes from installers.
For example some packages return error codes indicating the program is in use and should be exited before install.
OBS Studio returns "5" when the package is already running.
The text was updated successfully, but these errors were encountered: