Windows archive name e.g., Avogadro2.zip instead of Win64.exe.zip

[nbehrnd]

Is your feature request related to a problem? Please describe.
The download from the GitHub landing page, the nightly build for Windows is named Win64.exe.zip. Compared to the executable for Linux (i.e., Avogadro2.Appimage.zip), this is not very distinctive (e.g. for a search by keyword); it requires to open the archive to to recognize it is about Avogadro2.

Describe the solution you'd like
I propose to change the name of the archive provided for instance as Avogadro2.zip, or Avogadro2_win64.zip.

[ghutchis]

Makes sense. We can change the build scripts after this next release, e.g. the releases are Avogadro2-1.99.0-win64.exe

[matterhorn103]

IMO it would be good if either all the release artifacts included the version number or none of them did.

For what it's worth I was suggesting windows-x86_64 in that PR of mine rather than win64 because 1) that seems to be the usual way to denote the platform and 2) it allows distinction from Windows on ARM.

[nbehrnd]

@matterhorn103 Thank you for your input because at time filing the proposal, I wasn't aware this could become an issue for Windows (while well aware for Debian, and MacOS some colleagues use). Hence I support your argumentation.

By chance, do you happen to know if GitHub will set up a runner image for this (Windows 64bit ARM) architecture? Because i) the list of currently available picks (link) doesn't list it (yet) though it mentions a Windows Server 2025 beta image. And ii) because the reference executables of InChI trust (landing page) only discern between 32/64 bit on one side, and Windows and Unix-like (except MacOS) on the other. Just today it was possible to close the issue of how to run the 32bit executable in an instance of Windows 64bit (x86_64) (link) -- likely, the maintainers in this (now more public) project might want to expand the scope of their checks accordingly.

[matterhorn103]

ARM runners are available for Windows and Linux, just not for free.

I don't imagine they'll become freely available unless ARM achieves a significant install base on the respective platform. For Mac they kind of have to make both available since Apple switched straight from all their devices being x86 to all being ARM.

[matterhorn103]

@nbehrnd Well that was true at the time but not for long, since yesterday GitHub announced free runners for ARM Linux. So maybe a future runner for ARM Windows isn't too distant a possibility.

[nbehrnd]

@ghutchis A follow-up of the initial post. While I observe the executable for Windows (nightly builds) carries a more descriptive name (at present Avogadro2-1.100.0-win64.exe), the enclosing archive still is stuck in an almost anonymous name of Win64.exe.zip.