I posted about this here
<a href="https://charon.konekopi.com/posts/archlinux_on_arm/" rel="nofollow">https://charon.konekopi.com/posts/archlinux_on_arm/</a><p>But to answer your question:<p>A lot of ALARM core repositories are out of date, their extra repositories are even worse. chromium has been broken for like 1.5 year or so (I think it's fixed recently). Can't really blame them, they need to support older armv7 hardwares. Their packages are also for armv7 instead of the aarch64 architectures used by a lot of tablets/PC nowadays, so there's a huge performance/compatibility tradeoff they're making.<p>Arch linux aarch64 port is as the name says, aarch64 only, the people don't really care for older RPi. And because their work lives on the official arch linux repo, the pkgbuilds by definition won't be out of date. However package building are still community maintained, and will be out of date in that regards.
Very interesting!
I'm going to have to test if I can switch my Asahi ALARM M1 Macbook to official repos. I know when I use the AUR for packages, they typically have both x86 and aarch64 paclage instructions, maybe 10% or so don't and then I just clone the file and add it in manually.