Could we do arch-specific revbumps of GCCs arch-specific?

[barracuda156]

gcc ports were just revbumped across the board for a non-functional arm64-specific change in [df82c95db246abbf58ba09929118138ce14d357b/macports-ports]

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.).

[cjones051073 (Chris Jones)]

Personally, I chose not to complicate the port files by going down the road of having to deal with arch specific revisions...

[ryandesign (Ryan Carsten Schmidt)]

If it saves hours or days of compilation time it might be worth it.