Hi,
I suggest letting the NSIS installer behave as a silent wrapper for
launching the setup.exe per default.
As of now the NSIS installer asks the user where to extract the
installation files (i.e. setup.exe, msi cabs etc.) For me this is an
unnecessary drop in usability for the typical user of the NSIS installer
(i.e. downloader).
Instead I suggest this:
Doubleclicking nsis_installer.exe should
1) silently unpack installation files to "$TEMP\PRODUCTNAMEPLACEHOLDER
PRODUCTVERSIONPLACEHOLDER Installation Files"
2) silently launch "$TEMP\PRODUCTNAMEPLACEHOLDER
PRODUCTVERSIONPLACEHOLDER Installation Files\setup.exe"
3) leave installation files in "$TEMP\PRODUCTNAMEPLACEHOLDER
PRODUCTVERSIONPLACEHOLDER Installation Files" in order to enable
Modify/repair (see
http://qa.openoffice.org/issues/show_bug.cgi?id=49861) - On Windows it
is quite common to leave installation files in $TEMP AFAIK.
4) silently exit NSIS wrapper immediately
Command line parameters can be passed from nsis_installer.exe to
setup.exe by using this premade function:
http://nsis.sourceforge.net/wiki/Get_command_line_parameters
A command line parameter such as -x could be offered for people such as
sysadmins that want to unpack installation files to a specific directory
without launching setup.exe.
Since no UI is involved with the silent NSIS wrapper it will silently
"fix" these issues, too:
http://qa.openoffice.org/issues/show_bug.cgi?id=48741
http://qa.openoffice.org/issues/show_bug.cgi?id=52862
Yes, I am biased :-) Since OOo 1.1.2 I have post-build wrapped the
Danish win32 installation files with a silent NSIS wrapper without
receiving a single support question. NSIS scripts available:
http://qa.openoffice.org/issues/show_bug.cgi?id=33117
Søren
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
