blob: 4260551a1dcd49c26be5daae5c940889980a22f8 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
OpenOffice.org Build 1.0.1 Personal Install How-To
Written by: Martin Blapp <mbr@freebsd.org>
OpenOffice.org will soon been installed in
${PREFIX}/OpenOffice.org1.0/
1 User installation
-------------------
1.1 OO.org installed from the ports collection
Once this is done you have to run "make install-user" as the
user you like to use OO.org and choose a standard workstation
installation.
1.2 OO.org installed as package
First check if procfs is running. OO.org setup does depend on
procfs and does crash without it. This dependency will be
removed in future, but at the moment it is needed.
Please read the procfs(5) manpage and ensure the the following
line is in /etc/fstab:
proc /proc procfs rw 0 0
If you have just installed OO.org as package, there is no
"make install-user" option available. Instead you'll have
to run as the user you like to use OO.org:
"${PREFIX}/bin/openoffice-setup" and choose a standard workstation
installation.
2 JDK-Installation
------------------
If OO.org asks you to choose the Java JDK during
"make install-user", you must choose the linux jdk1.3.1.
Native FreeBSD jdk1.3.1 does not work yet with FreeBSD
OO.org does ignore it.
3 Start OO.org
--------------
There are some wrappers installed for fast startup.
Add "${PREFIX}/bin/" to your PATH and you will be able
to use them.
${PREFIX}/bin/openoffice
${PREFIX}/bin/openoffice-sagenda
${PREFIX}/bin/openoffice-scalc
${PREFIX}/bin/openoffice-sdraw
${PREFIX}/bin/openoffice-setup
${PREFIX}/bin/openoffice-sfax
${PREFIX}/bin/openoffice-simpress
${PREFIX}/bin/openoffice-spadmin
${PREFIX}/bin/openoffice-sweb
${PREFIX}/bin/openoffice-swriter
4 Setup problems
----------------
If the setup complains about a missing file
"setup.ins", it's time to upgrade your FreeBSD system
to the lastest version. You will encounter this bug
only if your OS is older than FreeBSD 4.6 STABLE.
4.6 RELEASE is still affected.
|
