minitar ignores file permissions

[rmattes]

cl-minitar seems to ignore the exec-bit of files. This leaves shell scripts distibuted by quicklisp inaccessible (not that executable scripts are a great idea to start with, but this has bitten my during attempts to pack/deploy third-party code (Common Music 2) as a quicklisp packet).

[quicklisp]

What are the shell scripts for?

[rmattes]

Pretty much an old-fashioned way to detect the build environment (OS, architrecture etc.) In this case (cm2) the idea is to build a standalone executable as part of the compilation. This is, IMHO, nothing needed in times of ASDF and Quicklisp but stopped me from a quick-n-dirty port. And I think, in general, minitar should respect file permissions.

[quicklisp]

How does that work on Windows?

[rmattes]

Frankly, I have no idea ;-) I didn't write all this, I just wanted to deploy cm2 with quicklisp. As I said, I'm less concerned about this specific case (cm2 does more nasty things, like run a scheme->lisp compiler during asdf loading and manipulating the fasl locations etc.) I just stumbled over what I'd consider a small bug.

[quicklisp]

It's not too small - Quicklisp is a Common Lisp program, not a Unix program, and managing Unix permissions is not something I'm enthusiastic about.

[rmattes]

Well, I don't want to beat a dead horse, but tar as a file format is a specified in the POSIX-1 standard, and that contains header fields for file permissions as well as the user and group IDs. I have no idea how tar on Windows handles this.