site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Dec 11, 2006, at 5:22 PM, Frederik Seiffert wrote: John, John _______________________________________________ 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... 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. You can set the permissions right in PackageMaker. In PackageMaker 2.1 click the "File Permissions" button in the contents pane of your package project. Using "Apply Recommendations" should give you a good starting point. But that is just setting permissions before creating the package. If user jblow with uid 503 installs something, it should be owned by jblow 503, not jdaniel 501. I really don't use the PackageMaker GUI at all anymore. It is so much more powerful from the command line. I have one project where I do set the permissions (to root) before creating the installer. In this case, I copy all my install files to a temporary folder, set them to root, create the package, then get rid of those root files. Otherwise, it really screws up CVS. This email sent to site_archiver@lists.apple.com