[MacPorts] #70340: Could we do arch-specific revbumps of GCCs arch-specific?

[MacPorts]

#70340: Could we do arch-specific revbumps of GCCs arch-specific?
--------------------------+----------------------------------------
 Reporter:  barracuda156  |      Owner:  (none)
     Type:  defect        |     Status:  new
 Priority:  Normal        |  Milestone:
Component:  ports         |    Version:  2.9.3
 Keywords:                |       Port:  gcc14, gcc13, gcc12, gcc11
--------------------------+----------------------------------------
 gcc ports were just revbumped across the board for a non-functional
 arm64-specific change in https://github.com/macports/macports-
 ports/commit/df82c95db246abbf58ba09929118138ce14d357b

 The change itself is perhaps desirable (and must be also made for powerpc
 triples, which are still wrong), but it is very wasteful to force everyone
 rebuild gcc on all archs, when literally nothing has changed for those.
 (It is also wasteful for MacPorts infrastructure – buildbots could be
 doing instead something more useful.)

 This also happened earlier on a few occasions. For someone with a slow
 hardware such revbump may translate into many hours or days of
 compilation, with strictly identical outcome as before.

 What is the aim of doing it this way? It is really trivial to do it
 correctly, setting revisions per-arch when necessary. This is not needed
 for every port, of course, but for ports which may need several hours to
 build, it is justified.

 I got a fast PowerMac, but even in this case I either need to stupidly
 waste 10 hours on rebuilds (when I just built all this some days ago) or
 revert revbumping locally (and it is unreasonable to expect every MacPorts
 end-user to be aware of overlay repos, check GitHub commits on every
 change to determine if it is justified, etc.).

-- 
Ticket URL: <https://trac.macports.org/ticket/70340>
MacPorts <https://www.macports.org/>
Ports system for macOS