Git.Git winget update - improve process for update

[theclickman]

Hi,

when I update the Git.Git package from winget, it keep resetting the windows Integration.
From what I see in https://github.com/microsoft/winget-pkgs/pull/299104/files for example - Configuration included hardcoded component list. (Git.Git.installer.yaml line 10;
Custom: /COMPONENTS=icons,ext,gitlfs,assoc,assoc_sh,consolefont,windowsterminal,scalar
)

Can we avoid that component list and leave it to standard, default option the project team elected ? The installer would automatically carry over already selected component in update scenario if it was elected on original install.

Thanks

[SpecterShell]

These switches were added by others who would like some components to be enabled by default. For example, there are some issues and PRs proposing making the Windows Terminal integration component selected by default:

• [Package Issue]: Git.Git does not correctly enable Windows Terminal integration microsoft/winget-pkgs#173310
• Registering Git Profile for Windows Terminal on Git.Git manifests microsoft/winget-pkgs#110011
• [Package Issue]: Git.Git - enable Terminal integration microsoft/winget-pkgs#109915
• Update manifest: Git.Git version 2.46.0 microsoft/winget-pkgs#173749

Unfortunately, Inno Setup, the installer technology the Git installer is based on, doesn't provide switches to simply add/remove components. The only relevant switch is /COMPONENTS, which deselects all the components and then selects the specified ones.

I would recommend you to open an issue in the microsoft/winget-pkgs repo to make others aware of the issue. This repo does nothing to the switches but simply copying them from the previous version of manifests to the new ones. I didn't touch the switches either.

[SpecterShell]

A temporary solution is to append --override "/SP- /VERYSILENT /SUPPRESSMSGBOXES /NORESTART" after winget, which discards all the pre-defined silent installation switches and the hard-coded package custom switches

[theclickman]

Thanks for your answer, will do.
Too bad we cannot "save" somewhere in winget to apply that specific override automatically when dealing with a certain package, I would set it up and forget about it then - it would help keeping thing simple.
Thanks

[theclickman]

done - microsoft/winget-pkgs#300009