On Thu, Jan 09, 2020 at 05:23:16PM -0500, Ben Cotton wrote:
On Thu, Jan 9, 2020 at 5:03 PM Zbigniew Jędrzejewski-Szmek
> 4. This certainly needs to be a "system wide change" with the related
> additional info required for such changes. We certainly need releng
> to sign off on this.
Apart from potential capacity impacts, this seems self-contained.
Changes (in the sense of spec conditionals and such) to some
yet-undefined subset of packages may necessary (for example if the
architecture change has some effect on floating point computations,
this could have a wide impact on packages doing numerical tests). So
there is a potential for interaction with a large number of packagers.
System-wide changes are also more widely announced (for example they
are listed prominently in the release notes), which imo would be
appropriate for something like a new architecture.
Because of those two reasons, I'd argue that the category should be
changed, but if you disagree, let's not discuss this further.
grant that a reduced builder capacity would impact other contributors,
but that doesn't seem like the kind of case the system-wide change
definition is designed for.
The change owner (bookwar) has already opened a ticket with RelEng
and they will discuss what work is necessary for this at the next