Hi Christian,
[...]
What makes the soffice execuable so specific that the Debian ooffice
executable does not work? Please help us answering this question to
solve this Bug in Debian.
Nothing I guess...
It seems that debian just did not calls it soffice and is simply not found.
Not being able to find the installation without that startup-link is
nothing special either - since vanilla OOo is not spread across the
filesystem, but everything resides in one single prefix.
Debian calls the soffice exec in the last line:
-----%<-----
[EMAIL PROTECTED]:~$ cat /usr/bin/ooffice | grep soffice
exec "$SystemInstallDir/program/soffice", @ooo_argv
-----%<-----
file /usr/bin/soffice
/usr/bin/soffice: symbolic link to /etc/openoffice.org-2.0/program/soffice
And /etc/openoffice.org-2.0 is in turn a symlink to /opt/openoffice.org2.0
file /opt/openoffice.org2.0/program/soffice
/opt/openoffice.org2.0/program/soffice: Bourne shell script text
executable
And there you have it. A simple shell-cribt that sets up some
environment variable and then calls <itself>.bin (→ soffice.bin)
The link in /usr/bin, as well as the symlink in /etc is setup by the
desktop-integration packages.
I don't think you speak about Debian above, do you? Within a Debian
system you will fin openoffice in /usr/lib/openoffice/...
Greetings, Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
