site_archiver@lists.apple.com Delivered-To: Installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=nD+2t+aYubX6yAanNaf5dVokzaQXBYKpvrY56QlE6os=; b=BEQGNxWlbTfNCUBeKXmoa8FD5GQUfx1yhuLe30cXPkb3U2kuXdu5ipQhoXuaahBI0i fbPjWm++OI4EMN6k7wXaUf9R4CO/Ge+lrkHUaxGU58O4gfhNRbnp/3Flz7Y7rnBn3KC/ ya6nxmcH9qc6IWk61G95te6n3uVRCAMtvXia4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=sV+xVHgUHRaDSjBwYFkQsO4+jqWnutMNahtGaDjNcHjBJVmIKDXP6Dem8Qu5BJx50Q toKEGDgeKs15vpeem/46j5DEhklA874HgVkj5hqJYa9vx+Cxp2Fw6CrHkU2wmj4u86dK Q6X19eeXg5mmQSIMzx6PlUqpS1wpwkvlh5NsE= On Nov 12, 2010, at 5:01 PM, James Turner wrote: 2 things: - the ownership issue could be a bug in PackageMaker. _______________________________________________ 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... 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. - not a great idea to have your launchd executable in /Library/ Application Support (from a security point of view). This email sent to site_archiver@lists.apple.com