Upgrade from 0.91 and later
===========================
Just compile & run. No database changes. Good luck...
Installation
============
The program needs postgresql as server.
It has been tested with KDE 3.04 an postgresql 7.3
Compilation and installation of postgresql
==========================================
Most distributions include postgres packages. Sometimes the postgresql
database system is splitted into several packages. Make sure that you have
at least the server and the headers installed. The package with the
headers may be located in the devel-branch of the distribution.
Some versions of SuSE include broken pgsql-packages and don't compile.
Debian (sid) works well (2002-12-20).
It may be easier to compile postgresql on your own:
Get the postgresql-7.3.tar.gz package, unpack it and change to the
base directory. Type:
cd ./src
./configure
make all
Postgresql now lives in /usr/local/pgsql
Set the LD_LIBRARY_PATH (for example in /etc/profile)...
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/pgsql/lib
export $LD_LIBRARY_PATH
...or add the line "/usr/local/pgsql/lib" to
the /etc/ld.so.conf and run 'ldconfig' (depends on
your system, sometimes both methods are working).
You may want to add /usr/local/pgsql/bin to
your PATH environment variable.
Compilation and installation of kaspaliste
==========================================
In order to compile and install Kaspaliste on your
system, type the following in the base directory of
the Kaspaliste distribution:
./configure
make
make install
Since Kaspaliste uses autoconf you should have not
trouble compiling it - as long as you use the correct compiler.
Kaspaliste was developed with gcc 2.95.4. It compiles with
gcc 3.04 and gcc 3.2, too.
Update: current version compiles with 3.3.3.
I don't know if it compiles with gcc 2.96 since I don't have
redhat or mandrake.
Installation problems
=====================
Important: sometimes the configure-script is unable to figure out the
paths of neccessary packages.
./configure --help shows some options which allow the explicit specification
of the paths.
Debian (sid) needs a
./configure --with-qt-includes=/usr/include/qt3/ --with-qt-libraries=/usr/lib/qt3/
General structure of directories:
Nowadays every distribution seems to have its own idea where to store the files of the
kde system. If kaspaliste starts up, but you experience an "empty" graphical user interface,
then something is wrong with the paths.
Here is some advice to handle the problem manually:
add the option "--prefix=/tmp/kl" to the call of the configure-script.
Do a make all && make install. Go to /tmp/kl. The bin/kaspaliste goes to /usr/bin or
/usr/local/bin. Look for a directory "kde/share", eg. "/usr/local/kde/share" or
"/opt/kde/share" or the like. Copy the stuff in /tmp/kl/share/ to that directory.
Other distributions like debian do not hava a dedicated "kde" directory. They use
"/usr/share" as root directory for some of the kde stuff. Look out for "/usr/share/apps"
and copy the content of "/tmp/kl/share/apps/" to this directory. Do the same with
"applnk" and "icons". The docs are stored in "/usr/share/doc/kde/HTML/en/". The
config files are stored in /etc/kde3/.
Sorry for the inconvenience. If somebody has an idea how to simplify matters:
please drop me a mail.
There is a new version of kaspaliste available at sourceforge in the cvs.
It cirumvents these problems. Its working title is "literature".
postgresql
==========
Kaspaliste needs postgresql as server. You have to initialize the postgresql
manager if you don't have already an existing postgresql installation.
The parameter is the directory where the database should live
(e.g. /home/xyz/pgdata).
You can omit the parameter $PGDATA environment
variable is set.
initdb -D<MY_PGSQL_DATADIR>
Start the postmaster (Read the postmaster manpage for a more
sophisticated command line):
postmaster -D<MY_PGSQL_DATADIR>
First you have to create a database named kaspaliste:
createdb kaspaliste
Read the file kaspaliste/data/create.tables.sql from the
kaspaliste directory with the command:
psql kaspaliste -f create.tables.sql
Now you are ready to start the frontend.
Upgrading to a new postgres version (from kaspaliste >= 0.91)
============================================================
Major updates of postgresql require a dump/reload of the database
(consult the postgresql documentation). Use the 'pg_dump' utility
of the postgresql distribution to dump the database _before_
updating postgresql:
pg_dump kaspaliste -Ov > /tmp/dump.sql
...upgrade the database and reload...
psql kaspaliste -f /tmp/dump.sql
Upgrading to a new postgres version (from kaspaliste < 0.91)
============================================================
When upgrading to a new postgres version a dump/reload of the
database might be necessary. The 'pg_dump' utility of the postgres
distribution (at least older versions) does not dump large objects.
There are two little programs named 'loadlo' and 'unloadlo'
(not included in kaspaliste>v0.91, see above).
They read/write all large objects from/in a directory.
The directory has to be accessible by the server.
To make them work correctly it is important to preserve
the oids while dumping with the '-o' option of pg_dump. 'loadlo'
has to be run after loading the dumped script with psql by the
postgres superuser.:
dump old database...
md /tmp/dump
pg_dump kaspaliste -ov > /tmp/dump/dump.sql
unloadlo -o /tmp/dump
...upgrade database and reload...
psql kaspaliste -f /tmp/dump/dump.sql
loadlo -i /tmp/dump
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes a while. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Type `make install' to install the programs and any data files and
documentation.
4. You can remove the program binaries and object files from the
source code directory by typing `make clean'.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
