[MacPorts] #70622: noarch archives fail to extract on Mac OS X 10.4 Tiger

[MacPorts]

#70622: noarch archives fail to extract on Mac OS X 10.4 Tiger
------------------------+--------------------
  Reporter:  fhgwright  |      Owner:  (none)
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.10.1
Resolution:             |   Keywords:  tiger
      Port:             |
------------------------+--------------------

Comment (by ryandesign):

 While this ticket is about binary archives that we produce on our build
 system, we have also had several reports of source tarballs having been
 created by their developers in a way that Tiger could not extract them. So
 far, this only seemed to appear when extended attributes were
 inadvertently included in those tarballs, and so far upstreams have been
 willing to release repackaged versions omitting the extended attributes.
 However upstreams might not always be so accommodating, especially if on
 newer operating systems the default tar format has changed to one that
 Tiger cannot extract. Therefore it would be great if we could find a way
 to extract the new tar format on Tiger, both when extracting our binary
 archives and when extracting source tarballs, but I don't yet know how to
 do that. One source I found claims that the new format is a superset of
 the old format, implying that it should be possible, at least, to post-
 process a new tarball to convert it into an old tarball. One option, of
 course, it that we could start bundling a tar extraction utility such as
 libarchive with MacPorts and use that instead of the one that comes with
 macOS.

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