|Subject:||Bad options used with Archive::Tar|
In 1.94 CPAN switches from using the system tar and gzip binaries by default for extracting to using Archive::Tar by default for all non-bzip2 archives. This change prevents modules that rely on executable scripts from installing correctly (for instance, Mail::Spamassassin) due to flaws in the way Archive::Tar is being used. In particular, the comment on line 315 of Tarzip.pm is inaccurate: # Make sure AT does not use permissions in the archive # This leaves it to the user's umask instead local $Archive::Tar::CHMOD = 0; Without the chmod, files extracted by Archive::Tar will never have any executable permissions, regardless of umask. Unfortunately it doesn't seem there is any way to do the equivalent of --no-same-permissions with Archive::Tar. At the same time $Archive::Tar::CHOWN is left alone, so extracted files get the (wrong) ownership value contained in the archive.