To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=54917
------- Additional comments from [EMAIL PROTECTED] Thu Oct 19 07:42:57 -0700 2006 ------- Why multiple separate installation methods? Why not one good, all-purpose, coherent method that presents a user with a predictable installation regardless of the distribution medium? I was not sure how the Installshield setup worked. I figured that it may be possible to pass the path from NSIS to Installshield. I understand and completely agree with your reasoning for keeping NSIS "simple". The idea of creating a self-extracitng zip is a good one (essentially what I originally proposed). In my opinion, the best way to handle this is to have a self-extracting zip installer. You could open the program in a zip file utility to extract the msi if you want, or you could simply run the exe which would extract the contents and automatically execute the msi. To make things really clean and simple for the user, first extract everything temporarily to the Temp directory. Launch the msi file from there. As part of the msi installation process, copy the install sources to the directory specified in the msi installer (final OOo installation directory). At the end of the installation, the extracted files are automatically removed from the temp directory (7-Zip does this automatically when you create/run an install package - WinZip might have this capability too). If the msi file is unable to copy the install files from the Temp directory to the path specified (I don't know - I never worked with Installshield), a reasonable alternative would be to extract the install files to a sensible path like "C:\Program Files\Common Files\OpenOffice Installer" (without prompting the user - once again, gurus could simply upack the install files themselves and put the files anywhere they want). This would still allow the installer to be simplified, while copying the installation package to a place that makes sense. This method would run equally well from CD or web. It would provide an easy way to get at the msi file. It wouldn't leave anything strange on the user's PC. It would also not require any user intervention outside of the msi installation. This sort of scenario would be like most other installation programs on Windows - click on the file with the Computer and Software Box icon, watch the little progress bar as the installer extracts, start the installation, agree to the license without even reading it, etc. I used to distribute OOo 1.x at my local college on CD in this manner. Since the old installer had many, many files to it and was distributed in zip form, I simplified things by wrapping everything into a 7-Zip installer. The user could then simply double-click on a single file (without sorting through a huge directory of files to find it). The installer would ask "Do you want to install OpenOffice.org?". If the user clicked yes, the installation files were extracted (with a progress bar) to the user's Temp directory and the installer was launched. Upon completion of the install, the files were automatically removed from the Temp directory. I received a lot of good feedback - nobody had any troubles installing the program. I believe a similar method could be used with current versions while still maintaining the necessary installation files for maintenance. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
