[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 berg-michael):

 I tried my script above to produce test files on bsdtar 3.5.2/Catalina. I
 tested whether they could be extracted on 10.4. My findings indicate that
 the pax archive format - which is the default for newer macOS - is the
 culprit.


 In the text below, "doesn't work" means gnutar produced the usual Skipping
 to next header error on 10.4

 "works" means gnutar extracted the file as expected and exited normally.

 {{{
 tar -xOvjf archive_default.tbz2 ./+CONTENTS - doesn't work

 tar -xOvjf archive_pax.tbz2  ./+CONTENTS - doesn't work

 tar -xOvjf archive_no_xattrs.tbz2 ./+CONTENTS - doesn't work

 tar -xOvjf archive_pax_no_xattrs.tbz2 ./+CONTENTS - doesn't work

 tar -xOvjf archive_gnutar.tbz2 ./+CONTENTS - works

 tar -xOvjf archive_gnutar_no_xattrs.tbz2 ./+CONTENTS - works

 tar -xOvjf archive_ustar.tbz2 ./+CONTENTS - works

 tar -xOvjf archive_ustar_no_xattrs.tbz2 ./+CONTENTS - works

 }}}


 This implies to me that in base we should pass either --format ustar or
 --format gnutar when producing archives. --no-xattrs seems to have no
 effect so there's no reason to include it.

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