[MacPorts] #70622: automake @1.17_0 fails to install on 10.4

[MacPorts]

#70622: automake @1.17_0 fails to install on 10.4
------------------------+--------------------
  Reporter:  fhgwright  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.10.1
Resolution:             |   Keywords:
      Port:             |
------------------------+--------------------

Comment (by fhgwright):

 Replying to [comment:1 ryandesign]:
 > Since this has to do with binary archives, which are not under
 individual ports' control but are created at the direction of MacPorts
 base, this would be a base bug and not specific to automake.

 As I suspected.  That suggests making the summary more generic, which I
 don't have permissions to do.

 > I'm not aware of any change in how our binary archives are constructed.
 It may always have been the case that some or all archives created on
 newer macOS versions cannot be extracted on 10.4's version of tar, but
 that this has only become a problem since it has become possible for
 archives to be shared amongst OS versions (MacPorts 2.9.0?). I don't know
 which version of macOS created the automake 1.17 archive now on our
 servers.

 Given that this issue just appeared between last Saturday and a little
 over a week earlier, it's probably whatever the buildbots are currently
 using.

 > You could try creating any tar archive on macOS 14 or other newer OS
 versions and then try extracting it on 10.4. If it fails the same way, and
 if you can then find some flags or options that can be used to create an
 archive on newer macOS that can be extracted on older macOS, base can be
 updated to use those flags or options.

 If there's a read-side fix, that would be better, since it would be
 compatible with the existing archives. Though a write-side fix might be
 accompanied by a sweep to update the existing relevant archives (perhaps
 just by repackaging the existing tarballs, rather than rebuilding them).

 The immediate workaround is for users to set `buildfromsource` on 10.4 to
 `always` (which I've confirmed works).  If the problem can't be fixed
 soon, then it might make sense for base to make that the default on 10.4.
 That could even be done right away, to be reverted if and when a better
 fix comes along.

 It would also be helpful, albeit in a rather verbose way (and the error
 output from this is ''really'' verbose), to have a failure to extract a
 binary archive fall back to building from source, just as it would do if a
 suitable binary archive didn't exist.

-- 
Ticket URL: <https://trac.macports.org/ticket/70622#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS