Issue 108265 - setup silently removes old OOo version
Summary: setup silently removes old OOo version
Status: ACCEPTED
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: OOo 3.2 RC2
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-12 14:26 UTC by Frank Schönheit
Modified: 2013-08-07 15:26 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2010-01-12 14:26:49 UTC 
- installed OOo 3.1.1 (custom installation, removed quickstarter, added ActiveX
  control)
- installed OOo 3.2 RC 2 (custom installation, changed the installation folder,
  which was suggested to be the one where my OOo 3.1.1 was installed)
=> after the installation of OOo 3.2 was finished, my OOo 3.1.1 installation
   was gone

what the heck? Could I please decide *myself* what happens on my hard disc?!
Comment 1 ingo.schmidt-rosbiegal 2010-01-13 13:42:35 UTC 
There is a checkbox about deleting existing OOo installation, when an old OOo 2
can be updated to OOo 3. You can select, if you want to have an OOo 2 next to an
OOo 3 or not.
But you can always have only one OOo 3, and therefore every OOo 3 removes older
installations that are also OOo 3 automatically. That is the mechanism, that we
used in OOo 2 timeframe and now also for OOo 3. 

This is simply an update of an installed product. If we make this with a so
called "Major Upgrade" in Windows Installer terminology, this means that an
older product is uninstalled first and then the new product is installed. With
OOo 3.0.1 we were the first time able to make a so called "Minor Upgrade"
(because no files were shifted or removed in OOo) in which the installed product
is found (if there is one) and all components (again in Windows Installer
terminology) are updated. In the "Minor Upgrade" the user is not asked for path
selection or module selection. Minor Upgrade and Major Upgrade are both full
installation sets
.
In my opinion it is only a technical detail, if we make "Minor Upgrade" or
"Major Upgrade". In both cases the user has an updated version of his product
after this process. The old product is no longer required after this process.

And one more info: If we make a "Major Upgrade", we can leave the old product on
the computer, so that after the installation can be two products on the system
(with all the known problems). In a "Minor Upgrade" (that is much more
attractive) only the installed product is updated, so that only the one existing
product stays on the system.
Comment 2 ingo.schmidt-rosbiegal 2010-02-10 11:28:08 UTC 
Thinking about it for new installer and setting target 3.x