updating file properties for self-contained zip deployments #529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #336
The issue here is with the file permissions that get applied after mounting the zip files in our linux hosting environment. Some points:
dotnet AssemblyName.dll
).HostOS
value to decide how to apply itsExternalFileAttributes
: https://bitbucket.org/agalanin/fuse-zip/annotate/89545b47f19801ca298d37fcf460e4ed311dc6c0/lib/fuseZipData.cpp?at=master#fuseZipData.cpp-158:231.The fix here is to pull in a richer Zip library that allows us to manage that field and make sure it's set to Unix so that fuse-zip can properly apply the executable permissions.