https://issues.apache.org/ooo/show_bug.cgi?id=121481

            Bug ID: 121481
        Issue Type: DEFECT
           Summary: openoffice installs its own /ust/bin/soffice instead
                    of using debian alternatives system
    Classification: Application
           Product: installation
           Version: AOO 3.4.1
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ui
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]

Since the fork between LibreOffice and OpenOffice.org (now Apache OpenOffice),
both suites install an /usr/bin/soffice link directly on Debian systems.
This completely prevents users to install both on the same computer, despite
Debian does provide a fully mature way to support that: the alternatives.

This is particularly annnoying since /usr/bin/soffice is already a link, so
technically there is no point in forcing its destination at installation.

With the current setting, attempting to install the suite A when suite B has
been installed beforehand fails (whatever are A and B, the problem is the same
in both installation orders). The failure is that dpkg refuses to overwrite
/usr/bin/soffice since it is owned by the first package installed. Installation
can be force using dpkg only using the --force-overwrite flag. This is really
inconvenient and seems to contradict Debian installation rules. Even if people
manage to install both packages using dpkg and --force-overwrite, upgrading
also don't work and the same trick has to be reused to overwrite the link.

Apache OpenOffice (and LibreOffice too) should use the alternatives mechanism
to
set up the /usr/bin/soffice link on the Debian packaging system. Note that the
same bug report has already been filed on the Debian bug tracker for
LibreOffice (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695916).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

Reply via email to