Building rpms from tarballs are a major pain... just grab the src.rpm, build it on a system that is like all your target systems, and rebuild it with "rpmbuild --rebuild foo.src.rpm" . You'll only need to have rddtools, pcre, devel rpms installed on the system where you rebuild the rpm.
for example, I've rebuilt hobbit-4.2.0-1.src.rpm on a rh9 server. it kicked out 3 rpms: server, client, tools.
So far I've installed the client rpm onto dozens of rh9, fc3,fc4,fc6,el3,el4 boxes without having to install any other rpms.
hope that helps.
Daniel Bourque
Systems/Network Administrator
Weather Data Inc
Office (XXX) XXX-XXXX
Office (XXX) XXX-XXXX ext. XXXX
Mobile (XXX) XXX-XXXX
James Wade wrote:
Hello All,
We are using Fedora Core 3 for an in-house application suite.
I've loaded on Hobbit with no problems and everything is working,
but I compiled everything from source.
I also had to compile and install: Apache2, rrdtool, tcl, pcre, and libart
prior to compiling Hobbit.
These are development boxes which use Kickstart to install new
versions of the in-house applications.
I would like to create a single rpm's of Hobbit, Apache2,
rrdtool, tcl, pcre, and libart so that I can easily install Hobbit
during the Kickstart process.
I've never created an rpm of a software application. Can someone give
me some good pointers. I've dug through some of the docs,
but I'm still a bit rough on the process. I understand that some of the
applications have a file that I might be able to use in the process.
Thanks....James