site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com User-agent: Thunderbird 2.0.0.0 (Macintosh/20070326) Page 47 of the Software Delivery Guide says: Mike On May 2, 2007, at 4:45 PM, Mike wrote: Did you remove any extension from the script's filename? — F ... _______________________________________________ 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... "In managed installs, install operations allow you to configure the destination environment before the payload is copied to the file system and to perform additional processing afterward. To specify install operations, you use executable files (known as install operation executables) that Installer invokes at specific stages during an install, as described in “The Installation Process” (page 24). Install operation executables must be named according to the install operation you want to define. The files can be binary files or text files containing shell scripts. All install operations are optional. You define only the operations required by a packaged product. This chapter shows how you use install operation executables to define the install operations the Installer application performs in a managed install." So it would seem to be the case that, no, you can't use Ruby scripts in the installer. However, have you tried writing a shell script named postinstall and then executing the Ruby script from inside that? You could also write a small binary to run the Ruby script. That might work. Fritz Anderson wrote: The script needs to be named "postflight", not "postflight.sh" for example. Yes, indeed I did. In fact, the script in question has always been named "postflight," and has never had any extension. (And I just now checked in a Finder Info window to verify this.) Anyway, if the script had the wrong name, surely Installer.app would never notice it at all, rather than log a message about failing to run it? An off-list correspondent suggests that a Ruby script — even in the form of an executable beginning with "#! /usr/bin/env ruby" — might be illegal in a postflight role. I doubt this, but is it possible? Fritz Anderson wrote: I have in my package a script named 'postflight'. It appears in the Contents/Resources directory of the package. It has the executable bits set. It is a Ruby script, with the first line being #! /usr/bin/env ruby . Whenever I try the installer, the only error appearing in the log is this: <date> <hostname> : Install failed: The following install step failed: run postflight script for <myPackageName> This email sent to site_archiver@lists.apple.com