how can an Installer plugin communicate with scripts?
how can an Installer plugin communicate with scripts?
- Subject: how can an Installer plugin communicate with scripts?
- From: Eric Slosser <email@hidden>
- Date: Wed, 12 Sep 2012 21:14:52 -0400
I'm trying to use PackageMaker to create an installer that will: - look in one of two places on the user's disk for a settings file
- look for the "install to" path in that file
- if it finds it,
- use it
- else
- put up UI that'll ask the user to pick the destination
I think the default UI for selecting a folder is too cumbersome, and I don't see how I could turn if off when step#3==true.
How can I communicate the destination from my plugin to the Installer?
If there's no way to do that, I'm planning on having the Installer put the stuff in /tmp, and using a postinstall or postflight script to move it from /tmp to the destination. What's the best way to communicate between a plugin and a script? I've tried shoving the value into -[InstallerSection sharedDictionary] or into the environment (man setenv 3), hoping that it would show up in the script (which is a bash script, if that matters), but that doesn't happen.
Other than doing something cheesy like having the plugin create a file in a static location, and reading that file from the script, what's the best way? |
_______________________________________________
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