Open DrHyde opened 3 years ago
For AIX the problem was reported already 10 years ago and became an issue 2019 #597. I was trapped by this problem yesterday on an AIX host and investigated it a little deeper. I have noticed that solaris is classified as an operating system with a bad tar:
use constant BAD_TAR => ($^O eq 'solaris' || $^O eq 'hpux');
This leads to a special untar backend (anonymous subroutine) that is indicated by the line
You have /usr/bin/tar, /usr/bin/gzip and /usr/bin/bzip2
You would reach the fallback untar backend Archive::Tar
only if either gzip or bzip2 or both could not be located. Maybe you want to give it a try to see if Archive::Tar
would work for you. I can solve my problem, if I am classifying AIX as an operating system with a bad tar too (#660).
I have a problem with
cpanm
on Solaris. I'm using cpanm 1.7044 on perl 5.32.0. Solaris has a rather out-of-datetar
which creatively misinterprets some modern tar-isms, and while I also have a more moderngtar
and alsoArchive::Tar
installed, there seems to be no way of tellingcpanm
to use either of them:If instead I do the install manually, using GNU tar to unpack the tarball:
Can I ask that the default be changed to GNU tar if available? If it's not installed as
tar
it can often be found asgtar
, and can be distinguished from othertar
s by the output from$tar --version
.Or alternatively that a new option be introduced to choose which tar executable to use.