On 7/1/25 5:57 PM, Levente Polyak wrote:
# First step for non-x86_64 contributions
Hey everyone,
I'd like to share my view on the first step for targeting non-x86_64 architectures in our packages. While our official infrastructure for non-x86 support isn't ready yet and will still take some time to materialize, I'd very much like to avoid siting on our hands until that day comes.
Very good news! I'm really happy to see that we are now willing to take a first step toward multi-arch contributions / support. :) On 7/2/25 12:20 PM, Christian Hesse wrote:
Carsten Haitzler <raster@rasterman.com> on Wed, 2025/07/02 11:00:
Next releases of anything I maintain shall be going arch=(any) as everything I maintain is fully portable anyway and always has been. My AUR pkgs already have a host of arch's in them and i'll simplify to any. No other changes needed.
That's probable a bad idea. :-o
That would set the arch "any" in the package metadata, which is not true if it contains architecture dependent data, like elf files.
Indeed, "any" doesn't mean "all" here. As said in the wiki [1], "any" is reserved for packages that can be built on any architecture, *and* once built, are *architecture-independent* in their compiled state (e.g. shell scripts, fonts, themes, etc...). [1] https://wiki.archlinux.org/title/PKGBUILD#arch -- Regards, Robin Candau / Antiz