Re: packagemaker not setting permissions correctly
Re: packagemaker not setting permissions correctly
- Subject: Re: packagemaker not setting permissions correctly
- From: Eli Bach <email@hidden>
- Date: Tue, 3 Mar 2009 12:39:13 -0800
On Mar 3, 2009, at 11:11 AM, Kevin Hoyt wrote:
Hi,
I have two packages that are behaving differently.
I'm using Package Maker 3.0.1 (172).
Targeting Mac OS 10.4.
I have used PM to set the permissions on the files so both packages to
have the same permissions on the Contents pane.
I have also made sure the files in my package source directory are
what I
want them to be after install.
I have removed my files, including the receipts.
After installation one of the packages has the expected
permissions. The
other one does not.
Any idea why they would be different and how I can force them to be
what I
want?
Do I really have to reset them in my post install/upgrade script? I
really hope not...
Kevin,
First, are you sure the permissions are correct in your package
(including on all the container folders, like /Application or
whereever your files get installed).
Second, and this is what got me as well, is that building using the
PackageMaker GUI, it does a verification/fix step that helpfully
'fixes' permissions to what it thinks they should be (which wasn't
correct for the files I was installing in /Library/LaunchDaemons).
To work around the GUI build problem, someone on this list helpfully
told me that I needed to build the package from the command line, with
permissions verification turned off, like this:
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/
PackageMaker --no-recommend <more options here>
Eli
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden