site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Thunderbird 2.0.0.19 (X11/20081209) Is there some way to get PackageMaker to skip this "fixing" step? _______________________________________________ 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/rcc2%40cornell.edu _______________________________________________ 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... When using PackageMaker from the command line, the "--no-recommend" option stops this behavior. Eli Bach wrote: Am I crazy or does PackageMaker 3.0.3 go out of it's way to apply incorrect permissions on files that go into /Library/LaunchDaemons/? For launchctl to work, permissions need to be 644, but PackageMaker installs them as 664. I've spent the time to create a source folder with the permissions I want for my files, and with Apple's permissions on their folders. When I get PackageMaker to build the package, it spends literally 5 minutes (as my package has a lot of files) "fixing" permissions to either be the same and/or to be incorrect. As a workaround, I've added a postinstall script that changes the permissions back, then calls launchctl to load the daemon. This email sent to rcc2@cornell.edu This email sent to site_archiver@lists.apple.com