For example, aarch64 is divided into aarch64_cortex-a53, aarch64_cortex-a72, and aarch64_generic, instead of using aarch64 directly like alpine?
If a third-party software needs to be installed on an arm64 platform running OpenWRT, is it necessary to compile multiple packages (.ipk or .apk) including aarch64_cortex-a53, aarch64_cortex-a72, and aarch64_generic?
Especially for Go language software packages, when compiling, there is no distinction between aarch64_cortex-a53, aarch64_cortex-a72, or aarch64_generic. As long as they are compiled by aarch64, they are the same. At this time, they still need to be packaged into three software packages, just because opkg or apk does not support the installation of aarch64 architecture software packages by default.
In addition, can apk install packages for other compatible architectures, such as installing aarch64_generic packages on aarch64_cortex-a53 platform? opkg can do this through the --add-arch parameter, does apk have a similar parameter?
As far as I know, apk does not support adding other compatible architectures, and can only install packages of the native architecture. If this is true, this will lead to unnecessary package building and storage. It is recommended that openwrt unify all aarch64 packages into aarch64, instead of continuing to distinguish between aarch64_cortex-a53, aarch64_cortex-a72, aarch64_generic