Re: Where do I put the custom Requirements Script
Re: Where do I put the custom Requirements Script
- Subject: Re: Where do I put the custom Requirements Script
- From: email@hidden
- Date: Tue, 13 Jan 2009 13:46:10 -0800
On Jan 13, 2009, at 7:25 AM, Kevin Kicklighter wrote:
On Jan 12, 2009, at 6:31 PM, email@hidden wrote:
On Jan 12, 2009, at 6:52 AM, Kevin Kicklighter wrote:
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.
How do I turn it on?
Switch to raw edition mode in PackageMaker, you should be able to see
the option (in the first tags).
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?
It's one of the approaches but others should work too.
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.
My $0.02
(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.
AFAIK, there are 2 kinds of requirements:
- InstallationCheck and VolumeCheck requirements. These are defined
in the distribution script.
- Choice requirements. These are defined in the distribution script too.
_______________________________________________
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