-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Complex installers #1242
Comments
This was included in the Apps & Features section for multiple entries. We still have additional work in the client to support upgrade scenarios and matching logic for list. winget-cli/schemas/JSON/manifests/v1.1.0/manifest.installer.1.1.0.json Lines 412 to 415 in 5a97e26
|
Another example would be various Autodesk programs. When you download "DWG TrueView" from https://www.autodesk.com/viewers (tab "Windows Viewer"), you will download an In the knowledge base of Autodesk is an example how to extract that sfx from the command line: https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/How-to-run-self-extraction-of-DWG-TrueView-2019-install-package-from-Command-Line.html |
…1796) * Modified the applicability check in `InstalledTypeComparator` to also consider the installer types listed under `AppsAndFeaturesEntries` * Extended string returned from `ExplainInapplicable` to also mention the installed type and other types accepted by the manifest. Closes #1242. Validated that upgrading PowerToys (mentioned in that issue) worked correctly using a local manifest edited to include the `AppsAndFeaturesEntries` and installed type `msi`.
Description of the new feature/enhancement
As we get closer to supporting .zip and standalone .exe installers, we need some additional mechanisms to identify a few different scenarios. These include what kind of an installer is inside of .zip files. It also includes scenarios where a package is distributed with a .exe installer, but it also contains an .msi installer (PowerToys).
Proposed technical implementation details (optional)
We would add a new node to the Installers called "NestedInstallerType".
This example would help fix the upgrade scenario related to PowerToys:
This example is for a nullsoft installer distributed inside of a .zip file, but this could also be .exe, inno, wix, etc.
This example is for a standalone / portable executable (these are not yet supported) inside of a .zip file.
The text was updated successfully, but these errors were encountered: