| You don't want a VolumeCheck. you want an InstallationCheck. IIRC VolumeCheck runs as the user gets to select where they want to install (its what can create those painful delays when you reach that stage). Its lets you disqualify volumes as possible install locations.
Two Links that may help (and where the basis for the relevant info in my page about it comes from):
http://developer.apple.com/Mac/library/documentation/DeveloperTools/Conceptual/SoftwareDistribution/Legacy_Requirements/Legacy_Requirements.html#//apple_ref/doc/uid/10000145i-CH13-SW1
http://developer.apple.com/Mac/library/documentation/DeveloperTools/Conceptual/SoftwareDistribution/Legacy_Requirements/Legacy_Requirements.html#//apple_ref/doc/uid/10000145i-CH13-1032302-CHEFBDAB
InstallationCheck and its corresponding strings file just has to be present inside the Resources folder, I don't think any other configuration is required. Adding them via Iceberg's additional resources should work, as long as they are named exactly right.
-nick
--
Nick Peelman email@hidden
"The secret to success is knowing who to blame for your failures."
On Mar 12, 2010, at 15:14, Xochitl Lunde wrote:
Ok,
I am still having a really hard time
figuring out how to use PackageMaker to do what I want. I have multiple
things that need to get installed.
* The root directory of my program
and its contents /Library/Application
Support/ (for now :/ )
* The launchd plist which starts
my daemon /Library/LaunchDaemons
* The launchd plist which starts
my assistant daemon /Library/LaunchDaemons
* The launchd plist which starts
my launch agent. /Library/LaunchAgents
I need to run a script before any of
these get installed, and then I need to run a script after all of them
have been installed. They are not separate "choices", you
have to install all of them. The part of the packagemaker GUI that
lets me define scripts is setup on the component. I cannot figure
out how to have these scripts defined for the "choice" or for
the entire package and not on the components. As soon as I add 2
components to my choice, PackageMaker changes and says I am now building
a distribution. Even if I remove everything from the package, it
does not go back to saying I'm making a "Package" instead of
a "Distribution". Why does it do this?
When I use Iceberg to make the same
package, I can define preflight/preinstall/postinstall/postflight really
easily. How do I do this using PackageMaker? I want to make
sure that my preinstall is run before any component is installed, and that
my postinstall is run after all components are installed.
Iceberg says I can add additional components,
so I add a 'VolumeCheck' script, but it looks like this never gets executed
even though it's part of my package. I have added a VolumeCheck script
that does nothing except exit with a value of 112 and my install doesn't
fail. I am guessing the script never gets run? I tried to get
a correct VolumeCheck script and strings using the info from http://www.peelman.us/tech/apple-packages/
.
Thanks,
Xo
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
|