site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com On Jan 12, 2009, at 6:31 PM, dev.iceberg@gmail.com wrote: On Jan 12, 2009, at 6:52 AM, Kevin Kicklighter wrote: How do I turn it on? It's one of the approaches but others should work too. My $0.02 _______________________________________________ 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... I am running Leopard PackageMaker 3.0.2 (174) and am trying to use a Requirements script to test a condition prior to installing. PackageMaker lets me select "Result of Script" , I can choose my script to run and enter my failure message, title and Message. However, the actual script does not get included in the package that is built. Also, I'm using minimum Target of Mac OS X v10.5 Leopard which is a flat file approach so I don't see how/where the package can even get the script. I also read somewhere that adding scripts is not supported on this flat file format. It is. If you're using a shell script as your requirements, you will need to check that the flag that allows external script to be run is turned on. In previous PackageMaker 3.x version, it was not turned on. After much reading of the mailing lists I decided to set the Minimum Target back down to Mac OS X v10.4 Tiger, and manually copied my script into the Resources folder that I created, and it worked. Is this really the approach we should take to include scripts in PackageMaker? Why does the UI allow me to choose the script that I run, but does not include it in the package? What am I missing? You should use the Flat Package Editor (*) utility to inspect the Flat metapackage (1) that was built by PackageMaker. The requirements are defined in the distribution script. (1) If you add a requirement (or a customized UI), PackageMaker will create a flat metapackage because requirements are not supported by flat package packages. Please clarify this. I think you CAN have requirements with the flat package, but not custom non-Javascript scripts. (*) It might be another name but I can't check it because my 10.5 machine died. Just control click on the package in the Package and select Open with in the Finder. So, all I did was take a 10.5 configuration, and set the Install Properties to 10.4. Now, neither preinstall nor preupgrade scripts run at all. This email sent to site_archiver@lists.apple.com