> The silent capabilities of the installer will do nicely in
> this regard...I can wrap it into my current NSIS script and
> simply call out to the installer. However, I need to create a
> empty database and initial user after install is complete. Is
> there any way to "hook" custom scripts into the installer's
> process? If not, what ways would you approach this? It'd have
> to be self-contained in some way, as I cannot guarantee any
> particular scripting language will be installed on the target
> machines.
Nope, no way to hook that in unless you want to build your own MSI. You
could create a hook in pginst.wxs and add the CA, and rebuild the MSI.
BUt then you'd have to rebuild the MSI yourself each time you get a new
version etc, which may not be what you want.
I don't know how NSIS works, but I'm sure you can write extension
functions for it, right? The safest way would be to write one in C
statically linked to libpq, and just have that one connect to the newly
installed database and create the required objects. That way you don't
rely on any external scripting languages or DLLs.
//Magnus