On Sat, Aug 15, 2026 at 09:36:00PM +0900, Simon Richter wrote: > Hi, Hi Simon,
> On 8/15/26 20:55, Simon McVittie wrote: > > > Adrian Bunk's comments elsewhere in this thread, that having the same > > package build differently on different architectures can end up being > > more work than having it build the same way everywhere, > > It also doesn't help -- anything that can be rebuilt can also be rebuilt for > amd64, more easily. having to maintain architecture-specific differences is a constant source of breakages, resulting in constant manual work. This is a problem we have all the time, already for the few cases where we have differences today. > > Perhaps it's a more efficient use of project members' limited time to > > keep building everything for every architecture unless/until a problem > > is seen, but be then be more willing to solve that problem via > > architecture-specific removals that we historically have been (similar > > to the removal of mozjs, gjs and GNOME Shell from armel in the past). > > Yes, but we'd also need more scalable infrastructure for that -- and that is > where a dedicated exclusion mechanism can provide a benefit over just > creating unfulfillable build dependencies. wanna-build is currently doing this ~ 5 times per hour for all 20 architectures. We do not have any performance problem there, and if there was one giving the VM more cores would be an option. It is not helpful when you are inventing claims like "we'd also need more scalable infrastructure" that are simply wrong. > Simon cu Adrian
