[MacPorts] #67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey, Ventura

[MacPorts]

#67336: BSD tar can create corrupted archives on Catalina, Big Sur, Monterey,
Ventura
---------------------+-------------------------------------------------
  Reporter:  catap   |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  base    |    Version:  2.8.1
Resolution:          |   Keywords:  catalina, bigsur, monterey, ventura
      Port:          |
---------------------+-------------------------------------------------

Comment (by ryandesign):

 Replying to [comment:21 ryandesign]:
 > LLVM tools create such sparse files.

 > at least on macOS 11 and later we could traverse the destroot and only
 use `purge` or `sleep` if there were any sparse files.

 On Monterey x86_64, reverting your change to `portarchivetype`, I tried
 destrooting pari and, every second or two, scanning the work directory for
 sparse files with Sparsity. (I scanned frequently since we know the
 problem fixes itself within 10 seconds of the files being created.) Aside
 from a log file in the configure phase, I didn't see any sparse files. I
 also tried reverting your change that blacklists Xcode clang; no change. I
 haven't seen the problem with the pari tbz2 archive on my system. If you
 consistently see the problem on your system, you could try scanning with
 Sparsity to see if we can confirm the theory that the problem occurs when
 there are sparse files.

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