			-= Gringotts installation instructions =-

Hi!
	you may have downloaded gringotts mainly in three forms: the
CVS repository image, the tarball or an RPM file. Here is how to handle
each of them:

							-= CVS=-
							
You can access to cvs repository of Pluto-devel with these data:

CVSROOT:	:pserver:anonymous@cvs.pluto.linux.it:/Devel
password:	anonymous

the directory to checkout is called "gringotts". If you download
Gringotts from CVS, it will miss all the various files generated
by the GNU build tools. So, you need to re-create them. In order
to do this, you'll need:

  Autoconf >= 2.52
  Automake >= 1.5

now, cd to the gringotts dir and type:

  aclocal
  autoconf
  autoheader
  automake --add-missing
  ./configure
  make dist

after these steps, you should have in your current directory a file
called gnomermind-x.x.x.tar.gz. Please read the next section to
learn how to handle it.

						  -= Tarball =-

So, you have a tar file, hm? These instructions will deal with a

gnomermind-x.x.x.tar.gz

file; if you've a .tar.bz2 one, you should know how to adapt them to
it. If not, just do a

  bunzip2 gnomermind-x.x.x.tar.bz2
  gzip --best gnomermind-x.x.x.tar

to convert it. Well, please unarchive it and go to its dir:

  tar xzf gnomermind-x.x.x.tar.gz
  cd gnomermind-x.x.x

in order to compile it, you will need:

  Gtk+ 2 (>= 1.3.13)
    http://www.gtk.org

  libmcrypt (>= 2.4.21)
    http://mcrypt.hellug.gr

  mhash (>= 0.8.13)
    http://mhash.sf.net

the specified package versions are simply those I use; if you have
older versions, gringotts may or may not compile. Once checked this,
do a simple

  ./configure
  make
  make install

sequence to install it. You may want to specify some options to the
configure script; type ./configure --help to learn more.

./configure accepts 2 non-standard options:

--enable-root-use
	if enabled, allows user root to use Gringotts. This is disabled
	by default, as it can lead to security problems.

--enable-safety-slowdowns
	turns on all the safety measures, even those who can cause a
	slowdown. If your Gringotts is too slow, you may wish to disable
	them, at price of a little less security. Enabled by default.

To build an RPM package from the tarball, simply do:

  rpm -tb gnomermind-x.x.x.tar.bz2

to build a binary package; notice that you'll need the bz2 tarball
(simply recompress it if you have a gz one). "-ts" will build a
source RPM. After this, read on.

							-= RPM =-

Finally, let's suppose you have an RPM. Gringotts behave just normally,
so to compile a source RPM you'll do:

  rpm --rebuild gnomermind-x.x.x-1.src.rpm

and to install a binary one:

  rpm -Uvh gnomermind-x.x.x-1.i386.rpm

easy, ain't it? Here we are, have fun!

	-- Mano :)