Apache OpenOffice (AOO) Bugzilla – Issue 7419
Upgrade feature
Last modified: 2003-09-08 16:53:51 UTC
I miss a possibility to upgrade an existing OO when installing a new one. Both using deb/rpm-packages (like mozilla) and using the installer. I think M$ Office works that way as well. An alternative, is that it transfers the settings to the new version, or some export/import settings-option. I think this is important for many users, and it is frustrating to set all settings again after installing a new version.
Duplicate *** This issue has been marked as a duplicate of 7236 ***
.
Is this really a duplicate? I was not talking about a patch-mechanism to reduce the download amount, but an ordinary download, just a normal upgrade possibility like some other programs has (for instance MS office i think).
I agree with the original poster, it's not just a matter of file size download. I have put a comment in the "duplicate" issue, because that one is opened and this one not :-)
From the debian package, where the maintainer also point out this problem (which I think is one of the most important ones) "Upgrade from 1.0.0 ================== Unfortunately, upstream has not provided an upgrade procedure from 1.0.0 to 1.0.1, so you must enter your user settings again. It seems tempting to add a script to the Debian package that attempts to perform the upgrade automatically, but I have experienced severe corruption in the user directory under 1.0.0, and am reluctant to blindly copy 1.0.0 user directories without being sure that sure corruption could not be transferred. Therefore, the two versions have completely different user directories: 1.0.0: ~/.openoffice 1.0.1: ~/.openoffice/1.0.1 You may find that you can transfer your settings using this command (untested!): cp -r ~/.openoffice/user ~/.openoffice/1.0.1" I have tried something like that last command, and it does NOT work. If i remember right, it caused the new openoffice to crash!
Still duplicate. *** This issue has been marked as a duplicate of 7236 ***
*** Issue 12236 has been marked as a duplicate of this issue. ***