On Thu, Nov 20, 2014 at 08:07:06AM +0100, Andreas Koenig wrote: > Chris, > > I don't know what the PaxHeaders problem here is about, do you? > > http://www.cpantesters.org/cpan/report/47822756 > > How invasive is that? How can it be stopped? >
When I extract that dist's tarball on that NetBSD box with /bin/tar I see a lot of the PaxHeaders.nnnnn directories. -bash-4.3$ ls Role-Pg-Roles-0.002.tar.gz -bash-4.3$ which tar /bin/tar -bash-4.3$ tar zxf Role-Pg-Roles-0.002.tar.gz -bash-4.3$ ls PaxHeaders.9275 Role-Pg-Roles-0.002 Role-Pg-Roles-0.002.tar.gz -bash-4.3$ ls Role-Pg-Roles-0.002/ Build.PL Changes LICENSE MANIFEST META.json META.yml Makefile.PL PaxHeaders.9275 README dist.ini lib t The PaxHeaders are pax header blocks: http://pubs.opengroup.org/onlinepubs/009695399/utilities/pax.html#tag_04_100_13_02 And this is incredibly ironic because on NetBSD, tar is basically the pax utility. gtar (which is GNU tar installed from pkgsrc) extracts the dist tarball without the PaxHeaders directories. As does Archive::Tar's ptar. I've updated Archive::Extract to favour gtar if on NetBSD (as it does already for OpenBSD and Solaris due to similiar issues with their native tar utilities). Many thanks, -- Chris Williams aka BinGOs PGP ID 0x4658671F http://www.gumbynet.org.uk ==========================
signature.asc
Description: Digital signature
