I have asked this question in the past with surprisingly ZERO response.
I really wish someone who knows would be kind enough to reply...
Our office currently has 1.1.4 installed on everyone's computer (yay!)... Upgrading 1.1.x has been virtually painless. I simply delete the old network installation on each computer, then install the new network version, then the next time the user logs in and the quickstarter starts, it prompts to upgrade the user installation... done.
I have always disliked the different numbers for each version, and I didn't want my 1.1.4 version sitting in a directory named 1.1.1, so I have always simply installed the 1.1.x network version to a directory named OOo1, and likewise, the User installs go into OOo1 as well. I am now doing the same thing for the 1.9.x snapshots - installing them into a directory named OOo2, and I then modify the bootstrap.ini file to install to the user directory named OOo2 (why, oh why, does this not get changed automatically when I change the default install directory path?).
With 1.9.x it won't work this way due to the new MSI installer.
So, I have tried uninstalling, then installing the new version, but I am not comfortable doing it this way since no one has responded to this question and *nothing* is said in any of the Help or Install Documentation I have read.
What is the *proper* method for upgrading the 1.9.x snapshots (and later the 2.x releases)?
Thanks
Charles
You are to be commended for leading your office to the light of OOo. One more step toward critical mass.
As for the "proper method" to upgrade the snapshots, there isn't one. One does _*NOT*_ upgrade to development software. You install it and test it. Period. It doesn't matter that you may be using the snapshot versions for real work (I do.), it is still testing. You are certainly justified to be concerned about multiple Install/Uninstall operations. The only protection available in that regard is a consistent and comprehensive backup process.
If you are concerned that when the time comes the upgrade process may not meet your needs, the best approach is to file a Request For Enhancement (RFE) through the Issue Tracking systems. That way it is assured to go straight to the people responsible for developing the software, it *will* be reviewed, and it will receive consideration for inclusion.
Doug
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
