There are many benefits to managing your software through the standard packaging system for your platform. This page is written for the benefit of:
- future madagascar developers who want to prepare packages for distribution
- system administrators who need to do their own packaging, such as for the purpose of easy, customized software management over a large number of machines
To make the RPMs, it is a good idea to first create a user just for this, i.e. makerpm. Then, install dependencies and set up. As root:
<bash> yum -y groupinstall "Development Tools" yum -y install rpmdevtools mock rpmlint </bash>
Log in as makerpm. Type: rpmdev-setuptree to create the ~/rpmbuild directory. Place the spec file in ~/rpmbuild/SPECS , then cd to that directory and run:
<bash> rpmbuild -ba madagascar.spec </bash>
If you want a log of the entire process, use something like:
<bash> rpmbuild -ba madagascar.spec |& tee ~/log_rpm.asc </bash>
If you want to make other RPM files, you may find useful to run
<bash> rpmlint yourfile.spec </bash>
Some warnings are OK. If you want to debug your experiments, you can comment the contents of the prep, build or clean sections in the spec file. For prep and build, you must have executed it uncommented at least once.
You may be able to QC the build with mock. For this, run as root:
<bash> yum -y install mock useradd -G mock makerpm </bash>
Then run it with mock -r fedora-12-x86_64 rebuild path_to_source_RPM .
Fedora's guide to creating RPM packages constitutes excellent further reading on the topic of making RPMs.