Rene Engelhard wrote:
Hi,
Am Montag 16 Januar 2006 16:47 schrieb Tom Schindl:
Well normally ooffice, oowriter, ... are bash-scripts or even perl (on
mandrake) starting soffice to popup the appropriate OpenOffice-Application.
On Mandrake for example one would have to same problem because:
ooffice2.0 does the following:
----------------8<----------------
#!/usr/bin/perl -w
my $SystemInstallDir = '/usr/lib/ooo-2.0';
...
exec "$SystemInstallDir/program/soffice", @ooo_argv
----------------8<----------------
yep. same script here on Debian. other path, though.
If it's really needed and would work I guess we could add some soffice
link (like /usr/bin/soffice -> /usrr/bin/ooffice -> calls the right soffice),
too..
/usr/bin/soffice should be a link directly to
<officepath>/program/soffice otherwise it won't work.
In the past the setup has inserted such a link and the bootstrap
mechanism uses this information (resolves the link and set an
appropriate classpath). But it seems that this search mechanism is not
reliable and the best way is to include the <office>/program directory
of the office you want to use in your PATH.
Today we insert a link staroffice or openoffice (somewhere) when i
remember correctly, maybe the bootstrap search algorithm is not adapted.
I will check it.
Juergen
Regards,
Rene
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
