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: Julian Devlin <email@hidden>
- Date: Wed, 1 Mar 2006 11:34:32 -0600
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. 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". I also get this message regardless of what my -f and -b roots are.
One thing that no one has mentioned is you could put a "sudo -v" at the beginning of the build.
That way the prompt for password does happen, but happens right away.
Then sudo the important step in your build, and unless it takes a long time to get to the step, the password won't have to be reentered.
Not a perfect fix, but at least you then type the password right away instead of sitting around watching the build, then having to notice the prompt.
-Julian
_______________________________________________
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