				Installing Meta-CVS

1. Verify system requirements.

   Meta-CVS requires CLISP 2.38 or newer. It is currently ported to two
   operating systems: GNU/Linux and Cygwin.  See the file PORT.

   Meta-CVS benefits from the presence of a /dev/urandom device.

   Here are some platforms that Meta-CVS has been successfully run on by its
   author:

     GNU/Linux (i686 Fedora Core 4, CLISP 2.38)
     Windows XP (Cygwin 1.5.22-1, CLISP 2.41)

   Stock installations of these platforms were used, using their binary packages   for CLISP, without compiling anything at all.

2. Obtain a binary package of CLISP or else build it. CLISP can be downloaded
   from http://clisp.sourceforge.net. Here is how to build CLISP, in one step:

   $ ./configure --build build-dir

   The name of the build directory can be anything you want; the
   choice ``build-dir'' is arbitrary. The directory is created and
   CLISP is built there. When the build is done, complete the installation:

   $ cd build-dir
   $ su root # if necessary, or other appropriate account
   $ make install 

   When CLISP is installed, you should be just able to run it using the
   ``clisp'' command, assuming that the installation directory 
   is in your PATH. 

3. Configure and build Meta-CVS. Note that using a separate build directory is
   not required, but is a cleaner approach. The default --prefix is 
   /usr/local.

   $ tar xzvf mcvs-<version>.tar.gz
   $ cd mcvs-<version>
   mcvs-<version> $ mkdir build-dir
   mcvs-<version> $ cd build-dir
   mcvs-<version>/build-dir $ ../configure
   mcvs-<version>/build-dir $ make
   mcvs-<version>/build-dir $ su root # if necessary
   mcvs-<version>/build-dir $ make install 

   Assuming that the  installation place is somewhere in your PATH,
   you should now be able to type ``mcvs'' and get the error
   message ``Meta-CVS requires a command argument.''.
   Also, the ``mcvs-debug'' command should be available, which is an
   uncompiled version of Meta-CVS that is useful for debugging.
