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: Peter Bierman <email@hidden>
- Date: Fri, 17 Feb 2006 11:15:56 -0800
At 4:24 PM -0800 2/16/06, Robert Simutis wrote:
If I run the PackageMaker CLI using "sudo" in front of the command,
it works, but prompts for a password. This is unusable for
automated builds, and developers who build installers aren't going
to want their builds to stop waiting for their password.
You can configure /etc/sudoers so that your automated script is not
promted for a passwrord.
Also, the users under which we all run all have admin access, so
I'm not sure why PackageMaker fails unless I do a "sudo".
Well, admin access is not equivalent to root access unless some
root-privileged tool decides to grant that access. 'sudo' is an
example of one tool configured to do so. PackageMaker needs root
access (not sure why in your case), so normally it will ask admin
users to confirm their password before granting the additional root
privileges.
-pmb
_______________________________________________
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