Subject: | Bad permissions in 1.10 tarball |
Hello Lorenz,
the permissions in the 1.10 tarball seem to be problematic. On a freebsd
system it looks like following:
$ tar tfvz /tmp/Tk-XPMs-1.10.tar.gz
drw-rw-rw- 0 domke 0 0 Nov 24 10:14 Tk-XPMs-1.10/
-rw-rw-rw- 0 domke 0 1088 Nov 24 10:14 Tk-XPMs-1.10/Changes
drw-rw-rw- 0 domke 0 0 Nov 24 10:14 Tk-XPMs-1.10/lib/
drw-rw-rw- 0 domke 0 0 Nov 24 10:14 Tk-XPMs-1.10/lib/Tk/
-rw-rw-rw- 0 domke 0 72422 Feb 25 2008 Tk-XPMs-1.10/lib/Tk/XPMs.pm
-rw-rw-rw- 0 domke 0 687 Jan 10 2006 Tk-XPMs-1.10/Makefile.PL
-rw-rw-rw- 0 domke 0 149 Feb 16 2005 Tk-XPMs-1.10/MANIFEST
-rw-rw-rw- 0 domke 0 443 Nov 24 10:14 Tk-XPMs-1.10/META.yml
-rw-rw-rw- 0 domke 0 544 Nov 24 10:06 Tk-XPMs-1.10/README
drw-rw-rw- 0 domke 0 0 Nov 24 10:14 Tk-XPMs-1.10/t/
-rw-rw-rw- 0 domke 0 2428 Nov 20 13:47 Tk-XPMs-1.10/t/Tk-XPMs.t
Note the missing "x" bits for the directories. This means, after
extracting the tarball it is not possible to change into the extracting
directory without adding the "x" bit first. Also, a build using the
CPAN.pm shell fails.
I saw this problem already in another distribution. I think there it was
due a bad gnutar version on Windows (IIRC, 1.12 was fine, but 1.13 did
bad things).
Regards,
Slaven