WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Currently, the implementation of the portable install flow differs for manifests that specify a portable installertype and manifests that specify nested portable(s) contained inside a zip package. For the single portable scenario, we record all of the installation metadata in ARP. I would ideally like all portable installs to be recorded to the index as this would be a more maintainable solution long term and only require a single location for capturing portable install metadata.
Steps to reproduce
N/A
Expected behavior
I expect all portable install metadata to be recorded in the portable db index.
Actual behavior
Currently split implementation between recording to ARP and recording to the portable db index.
Environment
Windows Package Manager (Preview) v1.5.441-preview
Trenly
commented
1 year ago
Brief description of your issue
Currently, the implementation of the portable install flow differs for manifests that specify a portable installertype and manifests that specify nested portable(s) contained inside a zip package. For the single portable scenario, we record all of the installation metadata in ARP. I would ideally like all portable installs to be recorded to the index as this would be a more maintainable solution long term and only require a single location for capturing portable install metadata.
Steps to reproduce
N/A
Expected behavior
I expect all portable install metadata to be recorded in the portable db index.
Actual behavior
Currently split implementation between recording to ARP and recording to the portable db index.
Environment