Building an RPM
 | NOTE |
|---|---|
For reasons explained in the Section called Integrity of the executable in the chapter called Security Design>, we do not recommend to distribute binary RPMs to third parties (and source RPMs only if build with make srpm-dist rather than make srpm). On the other hand, it is perfectly ok to use a self-built RPM to install/distribute samhain on your machine/within your own network. |
Single-host
If you want to create an RPM for a single-host version of samhain without any fancy options, you can just run
bash$ rpmbuild -ta samhain-version.tar.gz |
on the tarball (there is a default spec file in there).
| NOTE |
|---|---|
Due to the deficiencies of rpm, it is not easy to create a portable spec file (the spec file must include the list of installed files, but the paths are set as options to ./configure at build time by rpm, so they are not known it advance … pretty braindead system). The default spec file therefore may not work on all systems (it is tested on a RedHat system). |
Custom RPM
If you run ./configure in the source directory, a spec file samhain.spec will be created from samhain.spec.in. You can then use make rpm to create source and binary RPMs, or make srpm to create just the source RPM.
Of course, this is only useful for RPM-based systems, and also installing the RPM will not initialize the database automatically.
If anything fails during the build (and after installation has begun), just cd into the build directory and do a make uninstall && make uninstall-boot. If building for a non-RedHat system, the error messages will tell you which file paths in the spec file were incorrect.