Re: Automating PackageMaker CLI with Preserve Resource Forks option
site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On vendredi, mars 3, 2006, at 09:07 PM, Robert Simutis wrote: Could be because of bugs in SplitFork. _______________________________________________ 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... Thanks all for your responses and suggestions. I ended up modifying the "/private/etc/sudoers" file on my build machines to do the following: username ALL=NOPASSWD: /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker username ALL=NOPASSWD: /usr/sbin/chown *.pkg, /usr/sbin/chown *.mpkg, /bin/chmod *.pkg, /bin/chmod *.mpkg This allows the build script to run "PackageMaker" with sudo -- however the file ownership becomes root as a result, and thus it must be followed up with "sudo chmod" and "sudo chown" commands in order to restore permissions. It's still a puzzle why "sudo" is needed at all for resource forks but not data forks, but at least this gets around the automated builds problem. This email sent to site_archiver@lists.apple.com
participants (1)
-
Stéphane Sudre