Re: First step for non-x86_64 contributions

2025-07-01 Thread David Runge
On 2025-07-01 18:56:05 (+0200), Levente Polyak wrote: > On 7/1/25 6:44 PM, David Runge wrote: > > > ### Merge-request indicator > > > > > > All secondary architecture related merge-requests must be flagged with the > > > new `pkg::ports` GitLab label. It'll help separate them from the usual > > >

Re: First step for non-x86_64 contributions

2025-07-01 Thread Levente Polyak
On 7/1/25 6:44 PM, David Runge wrote: ### Merge-request indicator All secondary architecture related merge-requests must be flagged with the new `pkg::ports` GitLab label. It'll help separate them from the usual requests and allow interested packagers and contributors to filter on them globally,

Re: First step for non-x86_64 contributions

2025-07-01 Thread David Runge
Hey Levente, On 2025-07-01 17:57:37 (+0200), Levente Polyak wrote: > There's already a ton of community interest and effort around non-x86_64. > There's plenty of low hanging fruits and clean patches that are easy to > review, well contained, and good groundwork. So instead of waiting for the > pe

First step for non-x86_64 contributions

2025-07-01 Thread Levente Polyak
# 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