Changing architecture

[Graham David Rajan (voyager2saturn)]

So, there were a few packages which were mis-labelled as x86 and now I have changed to x64.
Since, there will also be a change in install location from "Program Files (x86)" to "Program Files" due to change in architecture I would like to know if the version which has the new architecture should have

UpgradeBehavior: Uninstall previous

this should uninstall the previous install (x86).

This currently affects 2 of my packages -

• New version: Audacious.MediaPlayer version 4.6.1 #413806
• New version: Intel.ThunderboltShare version 1.2.122.215 #423141

[Junaid Hussnain (Junaid-PK)]

Architecture is installer metadata; it does not tell the application which directory to use. Changing it from x86 to x64 therefore does not by itself require an uninstall-first upgrade.

Use the exact value

UpgradeBehavior: uninstallPrevious

only when the new installer cannot replace or migrate the existing installation and would otherwise leave both versions installed. WinGet implements that value literally: during an update it gets the old uninstall information and executes the uninstaller before starting the new installer. That can also remove application settings, so it should be based on tested installer behavior rather than the architecture change alone.

For these two cases:

• Intel.ThunderboltShare New version: Intel.ThunderboltShare version 1.2.122.215 #423141 has already been merged as x64 without UpgradeBehavior: uninstallPrevious.
• For Audacious.MediaPlayer, your PR notes that Audacious 4.4 and later already require 64-bit Windows. That makes the published x86 value look like incorrect metadata, not an actual 32-to-64-bit migration. The old and new manifests also use the same Nullsoft installer type and Audacious product code, so uninstall-first should not be added unless testing shows that the installer leaves the old copy behind.

The decisive test is to install the currently published version, run winget upgrade --manifest <new-manifest-directory>, and then verify that Apps & Features contains one entry and that the old installation is gone. If the upstream installer upgrades in place, leave UpgradeBehavior unset; if it leaves a side-by-side copy, then add uninstallPrevious.