                      INSTALLING MONOTHEKA

Short Answer:
^^^^^^^^^^^^^

        To build & install Monotheka in your system execute the
following commands in the unpacked directory:

        $> ./configure
        $> make
        $> su - root
        $> make install

        This will install a GNOME shortcut that you will find
in the 'Multimedia' part of you 'Applications' menu. Use it to
run the program and have fun. The database file (in case you'd
like to backup it) lies in ~/.gnome2/monotheka/monotheka.db


Long Answer:
^^^^^^^^^^^^

        Monotheka uses the monoBOIL auto-configuration script to
set up the build environment & installation properties. monoBOIL
is an auto-make clone and uses same/similar syntax. Basically it
tries to check the system sanity / dependencies / build files
from templates / create the makefile (non-recursive). 

        The most important command parameters you can issue to
monoBOIL (./configure) are: 

        --prefix=/path/to/ : The most important variable. In
most cases the only one you'll need to tweak. By default it
points to '/usr' . You MIGHT want to change it to '/usr/local'
(depends on the distribution). It specifies the basic root path
of all the user-related software. Other paths are built on top
of that path.

        --libdir=/path/to  : Top path were variables are
installed. By default it points to '$prefix/lib'. It's a good
default. Don't change it unless you know what you're doing. Most
of the Monotheka files are installed there + Plug-ins)

        --bindir=/path/to  : Path to the directory that contains
the user system-wide executables. By default it points to
'$prefix/bin'. It's a good default. Don't change it unless you
know what you're doing. 

        --datadir=/path/to : Path to so-called datadir. Should
point to directory, where GNOME files can be found. By default:
'$prefix/share' . It's very likely, that this is different for
your distro. 

        --pkgconfig=/path/ : Path to pkgconfig .pc
files. Usually this is /usr/lib/pkgconfig . It should get
auto-detected automatically.

Summing it all up... Typing:

        $> ./configure --prefix=/usr/local --datadir=/opt/gnome

... on a Novell Linux Desktop (example) should do the
trick. Same applies to Ubuntu (can someone confirm this?). 


monoBOIL:
^^^^^^^^^

        A few more words about monoBOIL. It was written because
automake drives me nuts. It's so UNCLEAN... ! Hundreds of
templates/macros/files/shit just to build one thing. Mono
software doesn't requite all the advanced host/machine checking,
hence monoBOIL.

        If you take a closer look at the "Generating Makefile"
part, you will notice that there is some smart logic
there. monoBOIL can automatically resolve dependency issues
between packages (directories) in one project. Using the 'boil'
files you can keep up the project logically and efficiently
organized. You can create libraries, executables and
collections. That's quite cool and simple.

        monoBOIL is not a brilliant piece of bash
scripting. It should be reworked at some point to support some
non-linux, non-x86 machinery.  
