https://bugs.freedesktop.org/show_bug.cgi?id=80278
Priority: medium
Bug ID: 80278
Assignee: [email protected]
Summary: Simplify side-by-side installation of productivity and
development/test versions
Severity: enhancement
Classification: Unclassified
OS: Windows (All)
Reporter: [email protected]
Hardware: x86-64 (AMD64)
Status: UNCONFIRMED
Version: 4.3.0.1 rc
Component: Installation
Product: LibreOffice
User story:
As a regular bug tester of LibreOffice I want a *quick and simple*, working way
to install a second (or third) version of Libreoffice besides my normal
(productive) installation in order to easily test the behaviour of several
versions without having to fear about corrupting (or erasing) my normal
installation.
Rationale:
I believe that if we make installing/uninstalling a LibO test version as easy
and comfortable as installing a production version then this will lower the
barrier for users to do bug testing and bug hunting.
Background:
Once in a while I post bugs and are asked to check if they already existed in
older versions (are regressions) or a are maybe fixed in the latest beta
versions. So far everytime I installed a version to test this it erased my
previous version which I had to re-install after the tests were finished. This
is annoying.
Today I tested the server installation as described on
https://wiki.documentfoundation.org/Installing_in_parallel#Windows.
I first tried the "Server GUI Setup 4.0.2", but it would show an error and
abort when trying to install the files of LibO 4.3.0.1 (RC1).
Then I followed the manual installation. This worked until the point when
trying to start the application. It complains it cannot find the Visual C++
Runtime DLLs although they are present in C:\Windows\System32 and the
documentation claims they should be put exactly there. So this didn't work
either.
I have now almost 1h wasted for nothing. This is perfect for putting off
possible engaged testers.
I therefore propose the following:
1. The normal windows installer UI should get an option to perform a
"side-by-side" (or "self-contained") installation not touching any already
installed instance of LibO or OOo.
2. This option should be offered to the user either
- if the installer detects another installed version on the machine or
- if the installer was started with a certain command line parameter or
- always. I leave this up to you.
3. The installer should then install LibO just as conveniently as with a normal
install. It should configure LibO to store the preferences within the
installation directory (as the server installation does), It should also create
the usual links in the start menu *besides* the existing links. (The user might
specify separate path in start menu for the.)
4. During such "side-by-side" installation the installer might ask the user to
change the file type associations to the new installation (so .odf or .doc
files open with the new instance), but this should be *disabled by default*
because usually the productive installation is supposed to work like it did
before, including being responsible for opening documents by default.
5. There should be no need to copy Windows DLLs from one place to another!
6. The installation should create an entry in the list of installed
applications under Windows in order to remove the installation just like any
other application.
Do I ask for too much?
----
Tested on Win7 HP 64 Bit.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
