I. Requirements

  GTK 2.2.x or higher
  PostgreSQL v7.3.x or higher
  The GNOME 2 Libraries

II. Make and Install

This is a two step process.  You MUST perform both steps.

Step #1: Building and Installing

Assuming that you have GTK and PostgreSQL installed correctly, all you
should have to do to build PRepS is:

./configure  --localstatedir=/var/lib
make
#become root if necessary
make install

See ./configure --help for a detailed list of all of the arguments that 
configure understands.  

Of note is:
--prefix=DIR  Directory where PRepS will be installed.
--with-pgconfdir=DIR
  Prefix where pg_config can be found.  The configure script needs
  to use pg_config in order to set up the Makefile's for your
  PostgreSQL installation.  You only need to use this option if
  pg_config is not in your PATH.
--localstatedir  modifiable single-machine data - this directory needs to
  be the base directory where the scroolkeeper database resides.  For most
  Linux distrubutions, this is /var/lib.


Step #2a: Creating a database (see step #2b if you are upgrading PRepS)
Step #2b: Updating an existing PRepS database
  Both of these steps are now performed using the prepsdb_tool, which
  is a part of the PReps Tools package.  See the INSTALL file in that
  package for details on creating or updating databases.

Step #3: Running PRepS

To run PRepS on the new database, type:

   preps -d database_name

where database_name is the name you gave the database when you created it
in Step #2.  You do not need the '-d database_name' option if you are
connecting to the default 'myprs' database.

PRepS will attempt to log in to the database without a username or password
(PostgreSQL can default these from your environment).  If this fails,
PRepS will display the login dialog.  This way, the simplest security will
work without hassle.  At the same time PRepS should still work with sites
that have a more secure PostgreSQL setup.

Remember to create at least one project, and to select at least one
"Submitter" and one "Project Member" for that project.

For more information on PRepS, see the preps man page and read the HTML
documentation that is installed in $PREFIX/share/preps.


III. Common Installation Types

a.) Single Machine - This is the simplest installation.  The single
    machine is the database server and the client.  This is a common
    way to run in a "home" environment.

b.) Server w/ thin clients - Basically just like a single machine.
    The server contains the database server and the client 
    application.  Users log in to the server, map the X display back
    to their machines, and run preps.

c.) Client/Server - One machine is the database server.  This machine
    must have PostgreSQL fully installed as well as the preps server
    tools (libpreps and prepsdb_tool).

    Other machines (the clients) only need to have the PostgreSQL 
    libraries and the PRepS client installed.  Users run preps
    from their own machines, and specify the server name or address
    when logging in to the PRepS database.

enjoy!


$Id: INSTALL,v 1.11 2004/09/12 21:33:46 stuffle Exp $