On Wed, 2 Jul 2025 21:25:22 +0200 Levente Polyak <anthraxx@archlinux.org> said:
On 7/2/25 6:29 PM, Carsten Haitzler wrote:
On Wed, 2 Jul 2025 12:20:49 +0200 Christian Hesse <list@eworm.de> said:
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.
yeah. i just found out - i never did that before. i was assuming it'd use $ARCH ... what's would be the way to go for "this will work on any arch - it's portable" without having to just list every arch i can think of?
-- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
makepkg/pacman does not support a meta architecture like `all`. Packages will need to explicitly opt for all supported architectures we expect to ship in Arch Linux.
i had ignored this until now as arch was just x86-64... with the move to multi-arch support i had hoped i'd have a "ok - this packaged i know works on anything... so can i now just say that in the package" and know if there is a rebuild server for any given arch, it'll just work with my packages without further work. this would avoid pointless churn that every time someone wants to add more arch's ... you don't have to mobilize the entire packaging team for every package... you do it only for those packages that do have explicit arch deps.
Please keep the arch=() array limited to architectures we actually do handle officially, which currently is only x86_64 :)
well the point of this mail is to begin preparing the way for handling other arch's - as above. i'd have wanted to just drop specific arch's entirely as i know they are a non-issue. it'd be a one-off fix to then never have to care again and i'd be prepared for the addition of multi-arch support in arch ahead of time. :) -- Carsten Haitzler <raster@archlinux.org> Carsten Haitzler <raster@rasterman.com>