Apache OpenOffice (AOO) Bugzilla – Issue 72560
Update installation should not use a new directory
Last modified: 2007-06-09 15:58:27 UTC
With OOo 2.1we can update 2.0.x. The default installation destination folder is named with the Office version '2.1'. Updating an existing 2.0.x version installed the default breaks all user settings loke desktop links to OOo he might have created. An Update should always use the same destination as the old version.
I do not like this change. In my opinion it is not a good idea, to install an OOo 2.2 into a directory OOo 2.1. For future installation sets, I would prefer an installation directory without versioning schema, to avoid such problems. IS -> FL: Perhaps UX has an opinion?
In this context the task i33449 becomes important again. Please also have a look at this task.
I have just tested this issue on my Windows XP system. I can not reproduce the behavior, because my system is automatically detecting that the location/folder has been changed and is automatically updating the URL of my test link (on the desktop). For the next major release we should go for "OpenOffice 3", just like we already do it for StarOffice 8. (see i33449 for details)
.
Nope: I've created two desktop links: One has been copied from the OOo 2.0 start menu entry, one has been created manually to scalc.exe in program folder. Both are not working any longer. If OOo has been rolled out on many desktops with manually created Desktop and Quickstarter links the new OOo 2.1 destination breaks these links.
reassigned
Hi Frank, code freeze is on Thursday the 25. January. Please handle / retarget this issue accordingly.
I have updated the target to 2.x. The current behavior still works for me.
*** Issue 74422 has been marked as a duplicate of this issue. ***
*** Issue 75002 has been marked as a duplicate of this issue. ***
IT's not a defect OOo works as designed. But I think this design is wrong in this case. This should be reworked. Installed addins and extensions are not working after upgrade if a new OOo destination has been choosen.
I disagree with accepting this as a bug. I am used to see that my WIN applications with regular update use a new program folder for "major" revisions like 2.x to 2.y, while smaller revisions (2.x.x to 2.x.y) will use the old program folder, and I think OOo should do so, too. If a user has good reasons to maintain the current folder for his programs, he can select that during the installation process. Addin handling (pls. see Issue 75002) should be improved with special OOo tools (may be a macro that comes up during first use of use of new installation and asks for "take over addin from ..." one by one). So I agree with 'Additional comments from of Thu Mar 1 08:44:27 +0000 2007'
I disagree with rainerbielefeld. OpenOffice is the only desktop office suite I know of that installs itself into different directories for each version. In fact, it's the only folder out of 31 in my Windows "Program Files" directory that uses a versioning scheme. It's seems very counterintuitive, and I don't see the benefit. It would be much simpler if there was a single OpenOffice directory.
PS - This issue seems to be a duplicate of 33449.
*** Issue 76270 has been marked as a duplicate of this issue. ***
*** Issue 76457 has been marked as a duplicate of this issue. ***
Using rpm to install I think it's not possible to choose the path. (?) (If it was possible, I would name it only openoffice (or openoffice2) for OO2.0, OO2.1 and 2.2 ... Fortunately at least the user-preferences are set to such a folder, so they still work.) That's why I would prefere another installing-behaviour.
(Is OO "standalone"?) While the installation via rpm doesn't ask for a path, is it possible to rename the folder /opt/openoffice... after the installation with rpm? Or will this cause crashes of links in oo / in the whole system? If it was possible, one could name the folder always the same way and links from starters in nautilus, konqueror (kde), mc, ... would always work.
'man rpm' is your firend. There you'll find that you can give an rpm a new destination [--relocate <oldpath=newpath>]. And yes, OOo 2.x is relocatable. But you should adjust the links for your systemintegration. But this is something for the mailinglists.
Dear developers, issue http://qa.openoffice.org/issues/show_bug.cgi?id=33449 seems to be dup of this one. Please choose which one should be closed.
I decided to close this one in favor of http://qa.openoffice.org/issues/show_bug.cgi?id=33449. Copying CC, dependencies, blocks and target . Please transfer your votes. *** This issue has been marked as a duplicate of 33449 ***
Closing. Please transfer your votes to http://qa.openoffice.org/issues/show_bug.cgi? id=33449.