Export should sort and remove duplicates

[ascarter]

Description of the new feature/enhancement

winget export should sort the packages list alphabetically and should also remove duplicates. I think a useful case is to export and then hand-edit to remove packages you might not want for every machine. I also found a couple duplicates. I don't know if that is a bug or not but the identifiers are identical so seems unnecessary to have the duplicates in the list if it is not a bug.

Proposed technical implementation details (optional)

[denelon]

I noticed this same situation with Cura. The .exe installer puts a second entry into Add / Remove Programs. If you export and include versions, I'm guessing you might see the same behavior. We will look at removing duplicate entries in export if two versions of the same program are installed. We would likely keep the duplicates if you specify versions in the export.

[ascarter]

Agree to keep duplicates if using versions. The default option without versions though seems like filtering would be good.

[woutervd]

When running export, I see many entries for the same version of the Windows SDK (I have VS 2017, 2019, and 2022 installed).
"PackageIdentifier" : "Microsoft.WindowsSDK" Version" : "< 10.0.22000.832"

Removing duplicates like this would make a lot of sense.

[denelon]

When you see the "less than'<'" symbol, it means the package is using the "packageVersion" to tell the user which version of a package is installed (as opposed to the "displayVersion" field from Windows Apps & Features {registry key} ).

If we don't have a manifest for the specific versions installed, it will result in potentially multiple duplicates with "< the minimum manifest matching version".

[Trenly]

[Policy] Command-Export
[Policy] Area-Sorting

[denelon]

Documenting current behavior and the intended design here.

Current behavior. winget export writes packages in the raw order they come back from the installed-package search - there is no alphabetical sort and no duplicate removal in the export path. (The sorting that shipped for winget list/upgrade is display-only for the on-screen table and does not affect the exported JSON.) So the duplicate entries described in this thread - e.g., a package that registers two Apps & Features entries, or the same Microsoft.WindowsSDK version matching from multiple Visual Studio installs - still appear in the exported file.

Intended design when this is implemented.

• Default (no --include-versions): sort the package list by PackageIdentifier and remove duplicate identifiers, so a hand-editable, de-duplicated list is produced.
• With --include-versions: keep the entries as-is, since distinct versions are meaningful and shouldn't be collapsed.

The change is well-scoped: sort (and conditionally de-duplicate) source.Packages before serialization in the export flow. Tagging Help-Wanted - contributions welcome.

(Drafted with GitHub Copilot assistance.)