Re: Permissios of package contents
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:from:to:in-reply-to:subject :x-priority:references:message-id:content-type :content-transfer-encoding:mime-version:date:x-mailer; bh=ZAvZlTwwh2s0SQfbsnfHy6D6/WWIpBnQXg4Pq1PC9zc=; b=iMbW/bmd4SFFJz7DSmdfDMBgTup5cLoCCxRsi488KXTtgZZDgM3p70Pz9nEUJqZQxi UcCmOdC321F0Sz380NcspfmLijYQjP3x2nuE+HRuDA0LB8Nino0n8WcZ03SWtACbFoN2 ihpmyODN9PEU/A06cBgpdRt5GUUqXznG39p5o= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:in-reply-to:subject:x-priority:references:message-id :content-type:content-transfer-encoding:mime-version:date:x-mailer; b=T1q6WydtdSFTT3Xa1sx+NaJI8WDKpz0/NfqhQK6V5I17oADa0Z3u+Qi2iT4sDabWO0 yVxmkgUvkFcPSzY9uXMQOgXtoNWbrV9kLpk1oOXuoJ7/k2uy1wT4M9J2zYBakgvl6Zbh WfdlcfcfBxxGhGHMpiSyW3QXffrNVIUx9t2WI= On May 2, 2009, at 12:03 PM, Andrew Peckover wrote: Hi, Thanks, Andrew Andrew, This is the point in time where you want to look at build automation. Eli _______________________________________________ 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... I'm confused about the permissions that we set in PackageMaker in the Contents area. I have version 3.0.3. Well, permissions have always confused me so this is nothing new for me :) But what I'm wondering is what I should typically set the Owner and Group to be. By default it's usually set to "Owner: Andrew" (my account name) and "Group: staff". Somewhere in the PM documentation, I think it talked about it typically being set to Root / Admin, so that's what I've being doing. But I have a lot of installs to make, and I change the contents often, so I would prefer to just leave it at the default rather than constantly changing it to root/admin when that might not make any difference. I've done testing, and I can't see any problem leaving it at Andrew / Staff with all the 9 boxes checked, but then again I don't understand permissions very well... I just receive 1 warning during compile "Warning such and such file is world writable", which I just ignore and everything seems to work well. I have tested the Apply Recommendations button before, and I'm not entirely clear what this does so I just leave it alone. Generally I get more "warnings" after pressing the apply recommendations button. Also, my installs have hundreds, sometimes thousands of files in them so I can't be applying permissions to each file individually (not that I think I would need to)... All this stuff is a pain to do manually for each build you do, but if you create a shell script to fix up permissions and owner/group on all your files, as well as building the package (as I've found that the command-line tool for building packages also works better than the GUI build operation). And if you script fixing permissions/owner/group, you might as well carry on with scripting your app with xcodebuild and creating the folder that PackageMaker uses read it's contents. This email sent to site_archiver@lists.apple.com
participants (1)
-
Eli Bach