In our typical Linux installation we rely on a launcher called
/opt/openoffice4/program/soffice
which in turns executes
/opt/openoffice4/program/soffice.bin
The 'soffice.bin' name is not hard-coded, but computed in the former
script with
sd_binary=`basename "$0"`.bin
As observed on the users list
http://markmail.org/message/eihw7r66e2bb2giy
this breaks expectations when one is using a symlink (say,
"openoffice4") to /opt/openoffice4/program/soffice since then $0 would
be the symlink's name and not "soffice", so the launcher would try to
execute "openoffice4.bin" and this wouldn't work.
Is there any reason against having some additional checks in our
launcher, or even hardcode "soffice.bin" as executable name there? This
seems Linux (or UNIX-like) specific but I haven't checked on other systems.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
