Issue 72560 - Update installation should not use a new directory
Summary: Update installation should not use a new directory
Status: CLOSED DUPLICATE of issue 33449
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 2.1
Hardware: All Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: OOo 2.x
Assignee: frank.loehmann
QA Contact: issues@installation
Keywords: oooqa
: 74422 75002 76270 76457 (view as issue list)
Depends on: 76369 76371
Blocks: 75000
  Show dependency tree
Reported: 2006-12-14 09:14 UTC by Olaf Felka
Modified: 2007-06-09 15:58 UTC (History)
4 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Olaf Felka 2006-12-14 09:14:34 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.
Comment 1 2006-12-20 17:21:18 UTC
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? 
Comment 2 2007-01-04 14:51:39 UTC
In this context the task i33449 becomes important again. Please also have a look
at this task.
Comment 3 frank.loehmann 2007-01-04 16:22:35 UTC
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

For the next major release we should go for "OpenOffice 3", just like we already
do it for StarOffice 8. (see i33449 for details)
Comment 4 frank.loehmann 2007-01-04 16:23:38 UTC
Comment 5 Olaf Felka 2007-01-05 09:04:41 UTC
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.
Comment 6 Olaf Felka 2007-01-05 09:05:41 UTC
Comment 7 bettina.haberer 2007-01-22 14:22:29 UTC
Hi Frank, code freeze is on Thursday the 25. January. Please handle / retarget
this issue accordingly. 
Comment 8 frank.loehmann 2007-01-22 16:22:09 UTC
I have updated the target to 2.x. The current behavior still works for me.
Comment 9 Olaf Felka 2007-02-11 13:15:07 UTC
*** Issue 74422 has been marked as a duplicate of this issue. ***
Comment 10 kpalagin 2007-02-11 13:18:31 UTC
*** Issue 74422 has been marked as a duplicate of this issue. ***
Comment 11 kpalagin 2007-02-11 13:35:13 UTC
*** Issue 74422 has been marked as a duplicate of this issue. ***
Comment 12 Olaf Felka 2007-03-01 08:35:49 UTC
*** Issue 75002 has been marked as a duplicate of this issue. ***
Comment 13 Olaf Felka 2007-03-01 08:44:27 UTC
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.
Comment 14 Rainer Bielefeld 2007-03-01 09:00:13 UTC
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'
Comment 15 specialtouch 2007-04-01 08:22:04 UTC
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.
Comment 16 specialtouch 2007-04-01 08:22:39 UTC
PS - This issue seems to be a duplicate of 33449.
Comment 17 Olaf Felka 2007-04-16 09:51:43 UTC
*** Issue 76270 has been marked as a duplicate of this issue. ***
Comment 18 Olaf Felka 2007-04-17 17:31:17 UTC
*** Issue 76457 has been marked as a duplicate of this issue. ***
Comment 19 meywer 2007-04-18 09:34:59 UTC
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.
Comment 20 meywer 2007-04-25 09:20:29 UTC
(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.
Comment 21 Olaf Felka 2007-04-25 09:30:20 UTC
'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.
Comment 22 kpalagin 2007-05-06 10:03:50 UTC
Dear developers,
issue seems to be dup 
of  this one.
Please choose which one should be closed.
Comment 23 kpalagin 2007-05-06 10:38:17 UTC
I decided to close this one in favor of
Copying CC, dependencies, blocks and target .
Please transfer your votes.

*** This issue has been marked as a duplicate of 33449 ***
Comment 24 kpalagin 2007-06-09 15:58:27 UTC

Please transfer your votes to