Include ARP for uncorrelated apps in `winget export`
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
When using winget export -o <path>, any apps that cannot be correlated to a package from an available source are not exported to the JSON file. There exists a case where the app currently does not exist in any source, but, could be added to a source between the time of the export and the time of an import. It would be helpful if the app could be correlated at the time of import and imported, rather than being omitted entirely.
Proposed technical implementation details
Have an option or setting to include un-correlated apps in the export. Enabling this would place the ARP data for the applications into a new section within the resulting JSON file from winget export. Enhance winget import to check for this new section, if it is present, attempt correlation using the ARP data there - if a match is returned, install it.
What's ARP data? Would be great if you refrain from using new acronyms that already have a well known and established meaning since 20+ years. Or at least spell it out.
What's
ARP data? Would be great if you refrain from using new acronyms that already have a well known and established meaning since 20+ years. Or at least spell it out.
https://github.com/microsoft/winget-pkgs/blob/master/doc/FAQ.md#what-is-an-arp-entry
Typical large corp behavior:
- Let's invent another acronym using one which already have at least 3-4 different meanings, because we're too lazy to type, and we certainly doesn't want to speak or write in clear language. 🤦
This would be useful for dealing with the many packages which do not have a manifest, yet are vital to my company.