Bug #11322
closedCHIRP on Windows needs to show its version in "Programs and Features/Apps & Features" (registry subkey needs to be added by installer) to make it fully compatible with package managers like winget
0%
Description
I can't draw your attention to this problem any other way (it has been MONTHS since I reported this, but still no response), so I'm also marking it as a Bug (and I think I'm right to do so).
You guys need to make CHIRP show its version in Windows registry. The installer has to add registry subkey to make it fully compatible with winget, which would be able to show the correct (not "unknown") version of the currently installed program and users will be able to determine their program's version and possibly upgrade it to the new version.
Let's make CHIRP better together!
https://chirp.danplanet.com/issues/10163?tab=history
https://github.com/microsoft/winget-cli/issues/1255
Quotes from this github conversation:
"What method does winget use to determine app version? I would have expected it to query the properties of the program, but that does not seem to be the case, as winget shows the version as unknown for GPU-Z (techpowerup.gpu-z), while the actual application executable properties show 2.40.0.0 for both Product Version and File Version."
Response:
"It uses the ARP (Add and Remove Programs) information, which then is tied to the Registry keys. This is nothing new so this is the Developers fault."
Files
Updated by Dan Smith 12 months ago
- Is duplicate of Bug #10163: winget only installs version 20221025 added
Updated by Adam G 19 days ago
Hi folks, I came across this same issue. I don't believe it is a duplicate of #10163 - they are both related to Winget, but different issues.
This one is specific to the CHIRP-next executable itself, as opposed to how it is published to Winget.
See the attached image: in Control Panel (even on Windows 11), the version string is missing from the program. This missing value has nothing to do with Winget.
Could this issue be reopened please?
Looking around the repository, I don't see any references to how the executable is built for Windows - is there any documentation for that?