Date: Tue, 24 Aug 1999 13:34:41 -0700 (PDT) From: Pete Carah <pete@ns.altadena.net> To: wkt@cs.adfa.edu.au Cc: questions@freebsd.org Subject: notes about star office Message-ID: <199908242034.NAA80607@ns.altadena.net>
next in thread | raw e-mail | index | archive | help
Thanks for finding the problem and workaround with the newer tarball... I notice several folks wanting to get permission from stardivision to distribute things this way; it is probably better to get them to fix the underlying problem so the workaround isn't needed in the first place. There are several things that work better than your description indicate - 1. Install library problem is easiest fixed by just giving setenv LD_LIBRARY_PATH /tmp/sv001.tmp (or equivalent for the installer's shell) before running the initial setup. This is much easier than manually unpacking and changing the names from upper case. 2. After an install into /usr/local/Office51, change the line Mode = STANDALONE; to Mode = NETWORK; in /usr/local/Office51/instdb.ins. This removes the need for the symlink script, only installing a meg or so of per-user config stuff into ~/Office51; an advantage is that user's configs don't conflict. 3. .sversionrc ends up pointing to /usr/local/Office51 after all this. It needs to point to ~/Office51 (probably with an absolute path for ~). After all of these star office runs as intended with most files shared. (these were all gleaned from various notes to questions, and the notes in freebsdrocks)... I notice that application startup once in the staroffice desktop is SLOOOOWWWWW!!. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908242034.NAA80607>