Hi,
There are two conflicting requirements in this game. On one hand, people
want a self-contained installation set which can be unpacked anywhere,
and $instdir/program/soffice can start LO.
On the other hand, Linux distros want "system integration", where
documentation goes to /usr/share, binaries go to /usr/bin, etc.
The usual hack to resolve this conflict is that /usr/bin has symlinks to
$libdir/libreoffice/ where the installation set is stored. (Perhaps the
same is true for /usr/share.)
Regards,
Miklos
Attachment:
signature.asc
Description: Digital signature
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.