I've tried your suggestion, but unfortunately it won't work in this case too, since most of the preinstall scripts should use it and at this point the script hasn't been deployed yet. I can't move the content of those preinstall scripts to the postinstall scripts of those packages, because all these packages have a payload, which requires some operations to be done before the actual deploying. Right now, the only option, that comes to me in mind, is to echo the content of that script to /tmp and make it executable via the first preinstall script from the first hidden package, but I wanted to know if there can be done anything else.
On August 31, 2013 at 7:01:36 PM, Philip Petev (email@hidden) wrote: No, the Conor's solution is not an option in this case, because the package is intended to run on a PC, initially without any internet connection. On the other hand, I'm already using an invisible packages, one at the beginning of the distribution with no payload and with only preinstall script and one at the end, also with no payload and with only postinstall script (the dummy preflight/postflight technique), so I could make it your way. I wasn't sure if there could be another way... Anyway, thanks everyone!
|