site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com Iceberg-Dev <dev.iceberg@gmail.com> wrote on 03/03/2009 12:24:55 PM:
On Mar 3, 2009, at 8:11 PM, 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?
Are the permissions not correct on files or folders? The first thing
to check are that the permissions in the payload are correct. You
could use Pacifist to check this.
Thank you for pointing me to Pacifist. The files in the package do not have the same permissions as what is set in PM. Nor do they match what is in the package source directories. They should be: -r--r--r-- But are -rw-rw-r-- For the most part the files are data files that nobody should be even looking at. Nobody needs to be able to write to them, that is for certain. If it matters, every directory in the path as drwxrwxr-x
Do I really have to reset them in my post install/upgrade script?
No.