[MacPorts] #56182: current_versions.tcl, delete_old_archives.py should understand that ports don't always offer the same version to all systems

[MacPorts]

#56182: current_versions.tcl, delete_old_archives.py should understand that ports
don't always offer the same version to all systems
----------------------------+---------------------
 Reporter:  ryandesign      |      Owner:  admin@…
     Type:  defect          |     Status:  new
 Priority:  Normal          |  Milestone:
Component:  server/hosting  |    Version:
 Keywords:                  |       Port:
----------------------------+---------------------
 If I'm not mistaken, [browser:macports-
 infrastructure/jobs/current_versions.tcl current_versions.tcl] assumes
 that all versions of macOS have the same version of each port. This is not
 always the case; this is why we have separate portindexes for each version
 of macOS. A port might offer a different version depending on `os.major`,
 or `os.arch`, or even `configure.cxx_stdlib`. For example, libomp offers
 version 5.0.1 to libc++ systems but version 3.8.1 to libstdc++ systems.
 Even though 5.0.1 is the "current version" according to
 current_versions.tcl, we should not delete the 3.8.1 archive for libstdc++
 systems.

 In practice, I don't know how big a problem this is. [browser:macports-
 infrastructure/jobs/delete_old_archives.py delete_old_archives.py] doesn't
 delete all old archives; it leaves up to 200GB of old archives, preferring
 to first delete the archives that are oldest and largest. Even if, say,
 the libomp 3.8.1 libstdc++ archives got inadvertently deleted, the
 buildbot would eventually recreate them, and then those new archives would
 not be "old" so they wouldn't be as likely to be deleted again for awhile.

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