site_archiver@lists.apple.com Delivered-To: Installer-dev@lists.apple.com Apologies if this is a FAQ - none of the references I've found on the web have answered it. I have a package with three components; a regular .app bundle in /Applications, many support files to go in /Library/Application Support/MyApp and a launchd plist to go in /Library/LaunchDaemons. (The actual daemon executable and accompanying frameworks live in the AppSupport dir - the frameworks are also used by the user-facing .app) In my .pmdoc, I've set all the owner and group permissions 'correctly', i.e root/admin for everything, in particular set the owner, group and permissions such that launchd will accept the plist. Unfortunately when installing, most of the files (90%?) end up with my user and group, not those specified in the pmdoc. This means launchd won't load the plist, since it's deliberately picky about permissions and ownership. Have I misunderstood a fundamental concept in how this is supposed to work? All this is happening on 10.6, PackageMaker is invoked by the build scripts as: `/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker --doc MyApp.pmdoc --out myapp-installer.pkg` As far as I know there is nothing unusual or special about the pmdoc - it's completely ordinary in every way. Regards, James Turner _______________________________________________ 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