Re: Automating PackageMaker CLI with Preserve Resource Forks option
Re: Automating PackageMaker CLI with Preserve Resource Forks option
- Subject: Re: Automating PackageMaker CLI with Preserve Resource Forks option
- From: Stéphane Sudre <email@hidden>
- Date: Fri, 3 Mar 2006 23:22:01 +0100
On vendredi, mars 3, 2006, at 09:07 PM, Robert Simutis wrote:
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.
Could be because of bugs in SplitFork.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden