This seems like a false economy -- but.....
$INSTALLER_TEMP is documented. It is a secure location (created using mktemp-like tricks to avoid hackery), that is created at the beginning of the distribution and kept around until the end, when it is reaped. (Not 1000% sure exactly how long it takes to get reaped. I think soon.)
The other thing to know is that the installer installs packages in the order they appear in the choices-outline.
So you COULD copy stuff into $INSTALLER_TEMP at the beginning of the first install script, use it throughout your installation packages, then clean it up in the last script.
But as I said, it seems a false economy, saving some package size at the expense of development effort/slight risk.
On Aug 31, 2013, at 7:12 AM, Philip Petev <
email@hidden> wrote:
Yeah, I know about that, but these extra resources can be used only by the preinstall/postintall scripts of that package and the other packages can't. I was thinking of a script, which can be used anytime by any preinstall/postinstall package of any package inside the distribution.
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