To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=63630
------- Additional comments from [EMAIL PROTECTED] Fri May 25 07:57:07 +0000 2007 ------- > Also, IMHO end users (developers maybe not) would benefit from profile > migration (or copying) during install, so that they don't have to worry about > the details. This will only work for the user who is installing ooo, it will not work in a multi user environment where there are multiple users on the same machine. For this to work in a multiuser environment, it needs to be done as part of the first start wizard. The first start wizard should be used for most of the other items that you mention, including the copying of the spotlight plugin and running any appropriate scripts. I'll give 2 examples: EyeTV uses its first start wizard to install a small background program into /Library/Application Support/EyeTV/EyeTV Helper.app and /Library/Application Support/EyeTV/Wakein. A file is created for the storage of the channel tunings. This is done on every install so that these items are always installed and available at launch. Using a .pkg can cause a problem, as this fix cannot be done. An admin user is needed to do the first run. For Toast Titanium, there are items installed in the first run of Toast Titanum, where you are given an option to install some optional items in certain places. Again an admin user is required to do some of these installations, such as a preference pane to /Library/PreferencePanes/ and ~/Library/Contextual Menu Items/ - I believe that ooo is a big enough application to allow for a change in the installation behaviour. With the multiple applications the user will drag a folder containing several applications and possibly a support folder, which could be hidden. Also the ability for the application to repair its self is very useful to users. I personally have been caught out by Apple's iLife installers after an archive and install of Mac OS X. Other applications, which fix themselves, were no problem whatsoever, other than maybe a first run wizard showing up. > .pkg install allows us to show readme/license/any other text + errors (like > "cannot install on Jaguar") etc. to the user during _install time_, not during > runtime, which would make _every_ startup to go through a more complicated > process. You also want to have errors like, cannot run on system X due to problem Y on start up, rather than on installation, as someone could be running ooo through some old install, remotely, through a backup or through FireWire disk target startup mode. --------------------------------------------------------------------- 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]
