To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=93774
------- Additional comments from [email protected] Tue Jul 28 07:56:23 +0000 2009 ------- Multiple points to note: 1 At least some bash versions appear to produce inconsistent behavior with symlinks (tested on some Linux boxes with bash 3.1.17 and 3.2.48): # install OOo DEV300m53 unxlngi6.pro to /export/home/ME/test/opt/... > cd /export/home/ME > mkdir test2 > cd test2 > ln -s /export/home/ME/test/opt/openoffice.org3/program/swriter oowriter > ./oowriter ./oowriter: line 4: /export/home/ME/test2/soffice: No such file or directory ./oowriter: line 4: exec: /export/home/ME/test2/soffice: cannot execute: No such file or directory > ln -s /export/home/ME/test/opt/openoffice.org3/program/soffice > ./soffice # OOo starts up, close it with ^Q > ps -uME # see that indeed no soffice running > ./oowriter # OOo starts up with empty writer document 2 The soffice script has special code to "resolve [the] installation directory" (see tags/DEV300_m53/desktop/scripts/soffice.sh l. 52--63) which the swriter etc. scripts lack (they just try to start `dirname "$0"`/soffice, see tags/DEV300_m53/desktop/scripts/swriter.sh etc.). Extending the swriter etc. scripts similar to the soffice script would make the behavior shown under (1) above more consistent (the first call to ./oowriter would succeed), but that code is not perfect, either (it relies on parsing ls -l output, which cannot work in general). 3 The go-oo fork probably includes code intended to fix issue 83548 (see <http://www.openoffice.org/nonav/issues/showattachment.cgi/49948/fix-linkoo.diff>), which has an impact on how OOo resolves certain symlinks and might or might not have an influence on this issue. If anything, I could imagine fixing the swriter etc. scripts as described under (2). However, since that fix would not be perfect, either, I would rather ask macias to state whether or not he is fine with the current situation, and if it is OK for him, close the issue again without taking further steps. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- 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]
