Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi, Guiseppe,

On Tue, 2010-10-05 at 22:41 +0200, Giuseppe Castagno wrote:
 From what I understand, in OOo the class is used to look for the path
where OOo is installed and from there obtaining the URE path.

In OOo it works using the symlink:

$ ls -l $(which soffice)
lrwxrwxrwx 1 root root 36 2010-07-05 10:59 /usr/bin/soffice ->
/opt/openoffice.org3/program/soffice

But in LibO that symlink is:

$ ls -l $(which libreoffice)
lrwxrwxrwx 1 root root 21 2010-10-05 17:35 /usr/bin/libreoffice ->
/usr/bin/libreoffice3

That's the reason why I'm not sure whether it works.
For the InstallationFinder to work in LibO, the symlink should be
something as:

/usr/bin/libreoffice -> /opt/libreoffice3/program/soffice

The soffice that, I think, you are referring to, will stay the same.

The little hurdle is that the /opt/libreoffice3/program/soffice is a
script that sets some environment and launches `basename $0`.bin. As it
is it will break saying that there is
no /opt/libreoffice3/program/libreoffice.bin
This could work, only one would need to modify that script that first
looks for `basename $0`.bin and if it does not find it, looks for
soffice.bin. If a volunteer could do it in desktop/scripts/soffice.sh in
a posix compliant way that does not break anything on exotic platforms,
it would just be wonderful. I might just hardcode soffice.bin there for
the time being.

Cheers

Fridrich


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.