site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On lundi, décembre 11, 2006, at 11:28 PM, John Daniel wrote: _______________________________________________ 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... installer-dev'ers, After only a few trails and errors, I have packagemaker working the way I want and I'm quite happy with the results. However, the PackageMaker help and some Internet postings are saying that I may be doing some things incorrectly. So, here are my > questions: Do I have to set permissions before creating the package? Currently, I just package up all my files and set ownership and permissions with the postinstall/postupgrade script. This package runs with AdminAuthorization and creates root/wheel files in /Library and works perfectly. It seems to me that Root is the only uid that is the same on all systems. If you want to ensure that ownership and permissions are set appropriately, these scripts seem to be the only place to do it. Setting permissions in the postinstall or postupgrade script is not the best solution in theory. The reason behind this is that if we imagine that one day Disk Utility will also use Receipts in /Library/Receipts to repair permissions on disk, your package will describe incorrect permissions. Additionally, doing it this way, you can't use the option to only set the permissions of folders that do not exist. So for instance, if you're setting the permissions for /Library, you may not set the right permissions depending on the OS version. That being said, postinstall or postupgrade (but you could use postflight) used to be the only solution to set owner and group to root:wheel for StartupItems in /Library/StartupItems on 10.1 (and maybe 10.2). This email sent to site_archiver@lists.apple.com