[rtg] building RTG version 0.9 (building RPM for CentOS)

[Bart van den Heuvel]

Hello!

It's been a while. To make my life easy as an administrator I'm converting
tarball installs to RPM packages. At the moment i'm doing it for RTG (google
code cvs version 0.9) to run on CentOS. I will check it for Suse in the
future.  The build process is tedious:

1. Download the source
svn checkout *http*://rtg2.googlecode.com/svn/trunk/ rtg2-read-only

2. make sure that all the required packages are installed. My current list
(build only, not for running RTG)

BuildRequires: make
BuildRequires: make-g++
BuildRequires: libtool
BuildRequires: libtool-ltdl
BuildRequires: libtool-ltdl-devel
BuildRequires: libpng
BuildRequires: libpng-devel
BuildRequires: gd-devel
BuildRequires: mysql-devel
BuildRequires: byacc
BuildRequires: flex


3. remove libtool from the build directory, then create a symbolic link by
running "ln -s /usr/bin/libtool"
4. run "libtoolize --force" in the build directory
5. run ./configure
6. comment out the line "include ./$(DEPDIR)/cgi.Po" in cgilib-0.4/Makefile
7. make
8. make install

My questions:

1. my guess is that nobody else made spec file? Am i right?
2. I see two options in the mailinglist: comment out the cgi.Po line in the
make file or get the file from an earlier source version (i did not find
it). Which is best?
3. I run RTG with my own grahping (embedded in PHP), so i don't need the cgi
stuff (also i dont test if it works). Does one need cgi.Po?
4. any more tips on building RTG, suggestions for the RPM file?


-- 
Groeten,

Bart van den Heuvel

Any society that would give up a little liberty to gain a little security
will deserve neither and lose both.
Benjamin Franklin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.grdata.com/pipermail/rtg/attachments/20100304/b68dc469/attachment.html>