[Feature] More Architectures #6469
Description
Feature Request
Is your feature request related to a problem? Please describe.
Some programs use instructions that not all CPUs of an architecture have (AVX), and so they have multiple builds. This means you have to pick a build when creating a manifest (usually the more compatible one), or create multiple manifests. Both of these situations are subpar because it means either the user runs program that's slower than what's possible, or they have to consciously know that the program has multiple builds and pick the one that matches their specific machine, which breaks the ability to just export all installed apps and reinstall on another system.
Describe the solution you'd like
Another architecture added to the allowed keys, like how ARM64 was added, this would require a little bit more knowledge on the package maintainers side and would require scoop to detect what features your cpu supports. I suggest that the new architectures are named after the clang targets x86-64-v2, x86-64-v3, x86-64-v4. It could also be 64bit-v2, 64bit-v3, 64bit-v4, following after the current key names.
Describe alternatives you've considered
Simply creating multiple packages for each build