compressed_app can't unzip resource forks
Closed this issue · 4 comments
The compressed_app provider uses the unzip command, which doesn't understand the __MACOSX directory containing resource fork data that is created by e.g. the Finder. The provider needs to use ditto -xk <zipfile> <destinationdir> instead.
I don't imagine ditto is around on your average Linux box?
Sent from my iPhone
On Jul 6, 2013, at 11:39 PM, André Arko notifications@github.com wrote:
The compressed_app provider uses the unzip command, which doesn't understand the __MACOSX directory containing resource fork data that is created by e.g. the Finder. The provider needs to use ditto -xk instead.
—
Reply to this email directly or view it on GitHub.
I don't imagine it is, since (iirc) it's an Apple command. But losing resource forks and littering /Applications with __MACOSX folders isn't great either. :(
I really hate the idea of two code paths being required here, but if it's the only way to handle that stuff I guess we will have to.
Sent from my iPhone
On Jul 9, 2013, at 9:53 AM, André Arko notifications@github.com wrote:
I don't imagine it is, since (iirc) it's an Apple command. But losing resource forks and littering /Applications with __MACOSX folders isn't great either. :(
—
Reply to this email directly or view it on GitHub.
well, it's basically the case of .zips that are created on/for Macs having special data in them that unzip doesn't know how to handle :( so I'm pretty sure that it needs to be ditto on macs and unzip on non-macs.
On Jul 9, 2013, at 10:55 AM, Will Farrington notifications@github.com wrote:
I really hate the idea of two code paths being required here, but if it's the only way to handle that stuff I guess we will have to.
Sent from my iPhone
On Jul 9, 2013, at 9:53 AM, André Arko notifications@github.com wrote:
I don't imagine it is, since (iirc) it's an Apple command. But losing resource forks and littering /Applications with __MACOSX folders isn't great either. :(
—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.