Suggestion to Adopt More Intuitive Architecture Names in Installation Packages
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 26.4k
- Forks
- 1.7k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 50
Description
Description
I suggest renaming the architecture designations in the installation packages to enhance clarity for a broader audience. Specifically, changing 'amd64' to 'x86-64' could help distinguish it more clearly from 'arm64', and similarly changing 'i386' to 'x86' would also aid selection, both of which make it easier for non-technical users to identify the correct version for their needs, thereby preventing mix-ups between the mentioned architecture types.
App Version
Gopeed-v1.5.6-windows-amd64-portable
OS Version
Windows 11 23H2 22631.3296
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the installation-package configuration or release entry point that produces the Windows architecture names, then compare the labels used for amd64, arm64, and i386. Done means the generated package names use x86-64 and x86 as requested without changing the underlying architecture targets.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100