Re: 'ditto' troubles
Re: 'ditto' troubles
- Subject: Re: 'ditto' troubles
- From: Steve Cronin <email@hidden>
- Date: Tue, 23 Feb 2010 16:20:29 -0600
Fritz;
Thanks for the tip. Things so obvious after clarity has improved.
The brain can be its own worst enemy…
Anyway the deployed result was simply an empty directory containing the valid application.
Reworking the original build step to remove the --keepParent appears to have done the trick…
Thanks Again
Steve
On Feb 23, 2010, at 2:43 PM, Fritz Anderson wrote:
> On 23 Feb 2010, at 2:11 PM, Steve Cronin wrote:
>
>> I have all of this working including a build step that compresses the appropriate release version of Helper
>> (/usr/bin/ditto -c -k --sequesterRsrc --keepParent)
>>
>> At the time the user requests I initiate an NSTask and deploy:
>> NSTask *unzipTask=[[NSTask alloc] init];
>> [unzipTask setLaunchPath:@"/usr/bin/ditto"];
>> [unzipTask setArguments:[NSArray arrayWithObjects:@"-x",@"-k",sourcePath,targetPath,nil]];
>>
>> The problem is that the deployed Helper file has the 'X' icon and displays the "application is damaged.." message.
>>
>> If I take the Helper.zip file from the 'contents' and manually double click it then the decompression works fine….
>
> You don't say whether you made the intermediate test of running
>
> /usr/bin/ditto -x -k Helper.zip SomewhereElse.app
>
> There might be diagnostic output.
>
> Also, did try to determine in what sense the expanded application was damaged? Did you audit the expanded Info.plist and MacOS/Helper files? Permissions (especially x bit for MacOS/Helper)? `files MacOS/Helper`?
>
> — F
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden