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
Some applications return non-zero codes that are not errors. There should be a way for the client to know the difference between these codes and actual errors.
A key could be added to the manifest syntax to indicate which non-zero codes should be treated as success. The client could then treat these non-zero return codes as success.
This is the case with installers wrapped in a WinRAR self-extracting archive, for example (e.g. microsoft/winget-pkgs#535). RARSFX will return exit code 1000 if the installation succeeded, and any other code indicates an error.
Activity
chausner commentedon May 22, 2020
This is the case with installers wrapped in a WinRAR self-extracting archive, for example (e.g. microsoft/winget-pkgs#535). RARSFX will return exit code 1000 if the installation succeeded, and any other code indicates an error.
superusercode commentedon May 24, 2020
This also impacts adobe digital editions, and there are plenty more documented in installers listed on chocolatey/scoop https://chocolatey.org/packages/adobedigitaleditions#files.
denelon commentedon Jul 28, 2020
microsoft/winget-pkgs#132
denelon commentedon Jul 28, 2020
fixes microsoft/winget-pkgs#132
denelon commentedon May 3, 2021
This feature is complete with the v1.0 schema and the v0.3 client release.
Squashed 'src/Valijson/valijson/' changes from 2dfc7499..94d3bfd3
Squashed 'src/Valijson/valijson/' changes from 2dfc7499..94d3bfd3
Squashed 'src/Valijson/valijson/' changes from 2dfc7499..0b4771e2