Tobias Krais wrote:
Hi Stephan,
[..]
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.
Is it the case that on Debian there is an executable named "ooffice"
in $PATH but not an executable named "soffice"?
Yes.
Well, the OOo Java simple bootstrap mechanism needs to find an OOo
installation, and one of the things it tries out is to search for a
file named "soffice" in $PATH (other things are looking at an
explicitly set $UNO_PATH, for example).
OK, this means that would mean that a simple link to ooffice called
soffice should work, but it does not.
it can't work. The bootstrap mechanism searches for an soffice in the
path, links are resolved and when a executable is found (binary or
script) the mechanism expects that the executable is found in a office
program directory and the known directory structure is interpreted in
some way to bootstrap.
A link soffice to ooffice won't help because the ooffice script is in
usr/bin and the bootstrap mechanism will fail. In this case you have to
use the UNP_PATH environment variable.
Juergen
Both files, the /usr/lib/openoffice/program/soffice and the
/usr/bin/ooffice call the /usr/lib/openoffice/program/soffice.bin and do
some other things. And these other things make the difference. What is
there so special?
Greetings, Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
