On Wed, 2 Jul 2025 21:25:22 +0200 Levente Polyak said:
> On 7/2/25 6:29 PM, Carsten Haitzler wrote:
> > On Wed, 2 Jul 2025 12:20:49 +0200 Christian Hesse said:
> >
> >> Carsten Haitzler on Wed, 2025/07/02 11:00:
> >>> Next releases of anything I maintain shall be going arch=(any) as
> >>> ever
On 7/2/25 6:29 PM, Carsten Haitzler wrote:
On Wed, 2 Jul 2025 12:20:49 +0200 Christian Hesse said:
Carsten Haitzler 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 alre
On Wed, 2 Jul 2025 12:20:49 +0200 Christian Hesse said:
> Carsten Haitzler 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
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 ta
Carsten Haitzler 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 prob
On Tue, 1 Jul 2025 17:57:37 +0200 Levente Polyak said:
> # 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 ye
