Proposed F19 Feature: Apache OpenOffice

Andrea Pescetti pescetti at apache.org
Wed Feb 6 01:36:36 UTC 2013


Miloslav Trmač wrote:
> On Mon, Feb 4, 2013 at 7:31 AM, David Tardon wrote:
>> On Sun, Feb 03, 2013 at 11:26:35PM -0600, Chris Adams wrote:
>>> $ rpm -ql libreoffice-core | grep bin/ | xargs ls -ld
>>> -rwxr-xr-x. 1 root root 362 Dec  6 18:37 /usr/bin/libreoffice
>>> -rwxr-xr-x. 1 root root  32 Dec  6 18:37 /usr/bin/ooffice
>>> -rwxr-xr-x. 1 root root  39 Dec  6 18:37 /usr/bin/ooviewdoc
>>> lrwxrwxrwx. 1 root root  11 Jan  9 12:46 /usr/bin/openoffice.org ->  libreoffice
>>> lrwxrwxrwx. 1 root root  38 Jan  9 12:46 /usr/bin/soffice ->  /usr/lib64/libreoffice/program/soffice
>>> -rwxr-xr-x. 1 root root 360 Dec  6 18:37 /usr/bin/unopkg
>> There is also /usr/bin/oowriter, oocalc, ooimpress, oodraw and oobase
>> that belong to other libreoffice-* subpackages.
> The feature page only discusses the soffice link; what does the
> feature propose to do about the other conflicting files in /usr/bin?

As Stephan wrote, soffice is the main problem (and I wonder if unopkg is 
in the same situation or is not problematic).

I would find it just reasonable that openoffice.org and the oo* 
launchers are kept free for Apache OpenOffice. Using the aoo* convention 
for OpenOffice is not common: executables from other Apache projects are 
not prefixed with an "a" (i.e., Fedora doesn't have "ahttpd", "asvn" and 
so on). LibreOffice modules could reasonably adopt the lo* convention to 
reflect the current naming. Anyway, this is common sense rather than a 
source of package conflict, so if there are technical arguments against 
this we can surely discuss further.

About the "soffice" alias, it still breaks parallel installation in F18 
(just tried, the desktop integration from OpenOffice conflicts with 
libreoffice-core). It seems that the upstream LibreOffice packages no 
longer use the "soffice" alias (at least, the desktop integration only 
installs "libreoffice3.6"), while the upstream OpenOffice packages still 
use "soffice". Are Stephan's concerns about legacy applications still 
valid? Admitting that Alternatives is a suboptimal solution (at least 
because it's system-wide) what would be a solution that allows smooth 
operations of both LibreOffice and OpenOffice? As I wrote multiple 
times, the LibreOffice user experience must remain virtually unchanged; 
but OpenOffice should be in the condition to be installed and work properly.

Regards,
   Andrea.


More information about the devel mailing list