File: INSTALL

package info (click to toggle)
webdruid 0.5.4-5
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 2,236 kB
  • ctags: 806
  • sloc: ansic: 10,823; sh: 2,763; makefile: 162
file content (61 lines) | stat: -rw-r--r-- 2,020 bytes parent folder | download | duplicates (8)
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
The WebDruid 0.5.4 -- Installation instructions

This is a short HOWTO to build this software on your unix system.

What follows the '$' sign is to be entered at the command prompt.

1) Get the required software

The WebDruid depends on the following external software.
Between parentheses is the version i'm sure it works well
with - it's the one i use to develop the WebDruid.
It might work with other versions too, but i don't really want
to test it myself :-) :
  - zlib (1.2.1)
  - the GD graphics library version (>= 1.8.4)
  - Freetype 2 (2.1.7)
  - Freefont package: http://savannah.nongnu.org/projects/freefont/
    The FreeSerif font from this package is used by default by The WebDruid.
    You should get the fonts at the above URL and unpack them in the
    /usr/share/fonts/truetype/freefont directory.
  - a gettext compatible C library (recent GNU libc is Ok) OR an external libintl library
  - an iconv compatible C library (recent GNU libc is Ok) OR an external libiconv library
  - Berkeley DB 3 (3.2.9) - OPTIONAL
  - graphviz (1.10) - OPTIONAL

2) Extract the archive & go to the directory

$tar -jxvf webdruid-0.5.4.tar.bz2
$cd webdruid-0.5.4

3) Configure the WebDruid for your system.

$./configure

If you have installed Berkeley DB, you might want to turn on dns lookup feature
by using ./configure --enable-dns instead

4) Compile the WebDruid

$make

You will see warnings from your compiler that some symbols are defined but never
used. You can safely ignore them, this is because the file which generates these
errors is currently under heavy development.

5) Install

$su -c 'make install'

6) Test your setup

Get a bunch of Apache log files or (similar CLF logs), preferably for more than a month.
cd to the directory where the logs are

run :
$webdruid *.log.*

If you have warnings or failures from The WebDruid, you must have missed your setup somewhere.
Check the report you have just generated...whaaa...it's marvellous!!

You know have The WebDruid installed on your system.