Skip to content

Latest commit

 

History

History
35 lines (18 loc) · 947 Bytes

BuildRPM.md

File metadata and controls

35 lines (18 loc) · 947 Bytes

RPM Build Instructions

Why make an RPM?

For non-container environments, the scaffold must be deployed as an rpm.

RPM installation requirements

This RPM will fail to install if httpd is not installed on the target system.

Steps for creating a release rpm

The following steps can and should be automated. Automation using Jenkins has been postponed at this point.

Build the latest release and RPM

extension-scaffold/scripts/buildLatestReleaseAsRPM.sh

This script will checkout the latest 'release' branch and build an RPM.

Build the RPM

extension-scaffold/rpmbuild/build.sh

Keep in mind

Currently this script does not 'sign' the RPM. This would typically be done by a Jenkins build.

Some utility commands if you want to look inside the RPM

  • List files in the RPM: rpm -qlp
  • Show RPM package scripts: rpm -qp --scripts
  • Extract files from an RPM: rpm2cpio |cpio -idmv