Welcome to docs.opsview.com
Building the RPM's
Rebuilding from SRPM's
Not all variations of architectures are available for building Opsview - for this reason users with ppc or sparc processors will need to rebuild Opsview for themselves.
This can be done doing the following:
- Ensure rpmforge repos are enabled - see https://rpmrepo.org/RPMforge/Using
- Ensure the user
nagiosexists - useradd_-g_nagios_-g_nagcmd_nagios} - Install 'rpmbuild' - i.e. yum_install_rpm-build}
- Obtain the source rpm's from the download web site for base, perl, core and web
- Run the following commands as root
mkdir $HOME/opsview_tmp rpmbuild --buildroot=$HOME/opsview_tmp --rebuild opsview-base-<version>.src.rpm rpmbuild --buildroot=$HOME/opsview_tmp --rebuild opsview-perl-<version>.src.rpm
- If necessary, install any missing dependencies and rerun the rpmbuild steps
opsview-core and opsview-web do not need to be rebuild as they do not contain compiled code (only perl code and scripts) do rpm's with a matching version can be downloaded from the download site.
When completed, RPMs should be somewhere under /usr/src/redhat/RPMS/
Building from subversion/tarballs
To build directly from source (to apply your own patches to Nagios for example)
If working from SVN
- checkout the source repository
- cd into the top level directory
- run
make tar- this will create a tarball for opsview-base, opsview-core and opsview-web
You can now use rpmbuild against the tarfiles like this
- run
sudo rpmbuild –define “distribution <dist>” –clean –ta opsview-base*.tar.gzto create the rpm's
After the initial build is verified as working, you can then apply your own patches and rebuild as necessary. If using tarfiles, extract, patch and recreate them as needed before rerunning the rpmbuild command.
Trace: » opsviewplugins » internationalisation » configuration_generation » access » snmp » deprecated-release » upgradingperlmodules » rpm_opsview