Re: postflight script failed [SOLVED]
Re: postflight script failed [SOLVED]
- Subject: Re: postflight script failed [SOLVED]
- From: Fritz Anderson <email@hidden>
- Date: Fri, 4 May 2007 14:48:05 -0500
Changing the cookie from #!\<tab>/usr/bin/ruby to #!<space>/usr/bin/ruby solved the problem. I had a residual problem with my script, but was able to clean it up by writing the resulting exceptions to a log file (this cures Installer.app's not producing usable logs).
I find the Installer environment's choking on the tab, when bash did not, to be odd, but I chalk that up to the many mysteries of sh-vs-bash.
I thank you all for the good attention you paid my problem.
— F
On May 3, 2007, at 7:32 PM, Fritz Anderson wrote: On May 3, 2007, at 5:35 PM, Peter Bierman wrote: It does work with any UNIX executable.
You didn't specify the full path to ruby in your earlier example.
Does this work?
#!/usr/bin/ruby
And Stéphane Sudre, to the same effect:
You didn't mention whether changing the magic cookie improved the result or not. Did it?
I did try that. It didn't work.
H'm. I see that my Ruby script begins with #!\t/usr/bin/ruby (note the tab character). I'm not at my PackageMaker machine just now, so I can't verify till tomorrow morning whether that makes a difference.
However, bash would tolerate that form of the shebang line (I could run the script from the command line). Maybe the environment Installer.app uses is pickier.
|
_______________________________________________
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