1 -= Gringotts installation instructions =- 2 3Hi! 4 you may have downloaded gringotts mainly in three forms: the 5CVS repository image, the tarball or an RPM file. Here is how to handle 6each of them: 7 8 -= CVS=- 9 10You can access to cvs repository of Pluto-devel with these data: 11 12CVSROOT: :pserver:anonymous@cvs.pluto.linux.it:/Devel 13password: anonymous 14 15the directory to checkout is called "gringotts". If you download 16Gringotts from CVS, it will miss all the various files generated 17by the GNU build tools. So, you need to re-create them. In order 18to do this, you'll need: 19 20 Autoconf >= 2.52 21 Automake = 1.4.* or 1.6.* 22 23now, cd to the gringotts dir and type: 24 25 sh autogen.sh 26 ./configure 27 make dist 28 29after these steps, you should have in your current directory a file 30called gringotts-x.y.z.tar.gz. Please read the next section to 31learn how to handle it. 32 33 -= Tarball =- 34 35So, you have a tar file, hm? These instructions will deal with a 36 37gringotts-x.y.z.tar.gz 38 39file; if you've a .tar.bz2 one, you should know how to adapt them to 40it. If not, just do a 41 42 bunzip2 gringotts-x.y.z.tar.bz2 43 gzip --best gringotts-x.y.z.tar 44 45to convert it. Well, please unarchive it and go to its dir: 46 47 tar xzf gringotts-x.y.z.tar.gz 48 cd gringotts-x.y.z 49 50in order to compile it, you will need: 51 52 Gtk+ 2 (>= 1.3.13) 53 http://www.gtk.org 54 55 libGringotts 56 http://www.prosa.com/people/grizzo/libgringotts/ 57 58the specified package versions are simply those I use; if you have 59older versions, gringotts may or may not compile. Once checked this, 60do a simple 61 62 ./configure 63 make 64 make install 65 66sequence to install it. You may want to specify some options to the 67configure script; type ./configure --help to learn more. 68 69./configure currently accepts 4 non-standard options: 70 71--enable-env-check 72 at startup, it checks the environment variables, and reset 73 them to safe values. Necessary for a safe use of Gringotts, 74 but in some (rare) cases it can lead to incompatibilities. 75 76--enable-root-filter 77 normally, root user can't start Gringotts. This can be 78 avoided specifying a Gringotts commandline option; if you 79 want to make this unavoidable, use this ./configure switch. 80 81--enable-maintainer-mode 82 this enables some checks (assertions, MALLOC_CHECK_ env var) 83 useful for programmers, but unneeded to end users. 84 85To build an RPM package from the tarball, simply do: 86 87 rpm -tb --clean gringotts-x.y.z.tar.bz2 88 89or, in a rpm 4.1-based system such as RedHat 8.0, 90 91 rpmbuild -tb --clean gringotts-x.y.z.tar.bz2 92 93to build a binary package; notice that you'll need the bz2 tarball 94(simply recompress it if you have a gz one). "-ts" will build a 95source RPM. After this, read on. 96 97 -= RPM =- 98 99Finally, let's suppose you have an RPM. Gringotts behave just normally, 100so to compile a source RPM you'll do: 101 102 rpm --rebuild gringotts-x.y.z-1.src.rpm 103 104or, in a rpm 4.1-based system such as RedHat 8.0, 105 106 rpmbuild --rebuild gringotts-x.y.z-1.src.rpm 107 108To specify some configure flags for the compilation process, set the 109variable $GRG_COMPILE_FLAGS: 110 111 GRG_COMPILE_FLAGS="--enable-root-filter" rpm --rebuild [...] 112 113To install the binary one, you can do: 114 115 rpm -Uvh gringotts-x.y.z-1.i386.rpm 116 117easy, ain't it? Here we are, have fun! 118 119 -- Mano :) 120