Re: Using defaults command to modify Info.plist changes permissions
Re: Using defaults command to modify Info.plist changes permissions
- Subject: Re: Using defaults command to modify Info.plist changes permissions
- From: Clark Cox <email@hidden>
- Date: Tue, 15 Sep 2009 16:08:19 +0200
On Tue, Sep 15, 2009 at 2:43 AM, Chris Suter <email@hidden> wrote:
> Hi Jonathan,
> On Tue, Sep 15, 2009 at 7:52 AM, email@hidden
> <email@hidden> wrote:
>>
>> One of build phase script includes the perl variant of the following
>> terminal command to inject a build number into my info.plist
>>
>> defaults write /Users/Shared/Release/MyApp.app/contents/Info MyBuildNumber
>> 123
>>
>> Is it by design that the defaults command changes the access permissions
>> to 600 (ie: no access for anyone but the owner)?
>> defaults (1) doesn't mention this side effect. running on 10.6.
>>
>> The effect of this is to kill the app for users who are not the owner (at
>> launch the info.plist cannot be read, hence no principal class, hence no
>> launch).
>
> Try using /usr/libexec/PlistBuddy. Using the defaults tool to modify plists
> is deprecated I believe.
Indeed. /usr/bin/defaults is meant for editing user defaults, not for
general plist editing.
--
Clark S. Cox III
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden