zfdeploy.phar build does not preserve file permission

[metanav]

The zfdeploy.phar build command does not preserve the file permission in the created package. This functionality should be included as it would help in deployment process automation.

[weierophinney]

The patch above addresses this. Kind of. There are some limitations:

• Zip (and hence ZPK) as a format does not store file permissions. Cannot do anything about this.
• In my testing, it appears that PharData (which we use for creating tar and tar.gz/tgz archives) applies a umask, and, as such, all directories inside the archive get permissions of 0755, regardless of what the source directory was. The only way I can think of to fix this is to iterate through the original source directory, pull the matching file out of the archive, and call PharFileInfo::chmod() on it. I suspect this would be ridiculously slow, but will be trying it shortly.

That said, I did verify that the changes I introduced are correctly setting the directory and file permissions in the temporary directory we package from. The question is if we can find a routine that will ensure those permissions are retained in the package.

[weierophinney]

In doing some work on this, I discovered that "directories" in a PharData/Phar file are metadata only, and thus cannot accept a chmod operation (actually raises a fatal error when you try).

As such, I cannot do anything more on this. You will need to add some logic when deploying to set directory permissions if those present in the archives will not work.