RPM Packager Skill

Transform source code into installable RPM packages for CentOS/RHEL systems.

Quick Start

CODEBLOCK0

Workflow

1. Prepare Source Code

Ensure source code is ready:

• - Has a build system (Makefile, CMakeLists.txt, setup.py, etc.)
• Clean directory structure
• No build artifacts

2. Check Prerequisites

Required tools on CentOS/RHEL (requires sudo privileges):
CODEBLOCK1

Note: Installing system packages requires sudo privileges. The build process itself runs as your user account.

3. Run Build Script

CODEBLOCK2

4. Verify Output

Build produces:

• - Binary RPM: INLINECODE1
• Source RPM: INLINECODE2

5. Install & Test

CODEBLOCK3

SPEC File Customization

For complex packages, customize the SPEC file:

1. 1. Review template: See references/spec-template.md
2. Edit generated SPEC: Modify INLINECODE3
3. Rebuild: INLINECODE4

Common Customizations

Add dependencies:
CODEBLOCK4

Custom install paths:
CODEBLOCK5

Include documentation:
CODEBLOCK6

Build for Different CentOS Versions

Use mock for clean builds targeting specific versions:

CODEBLOCK7

Environment Variables

Troubleshooting

Build fails with "No such file or directory"

• - Check BuildRequires for missing tools
• Verify source tarball extracts correctly

RPM installs but command not found

• - Ensure %files section includes correct paths
• Check executable permissions in INLINECODE11

Dependency errors during install

• - Add missing Requires entries to SPEC file
• Use yum localinstall instead of rpm -i for auto-dependency resolution

Output Locations

After successful build:

• - Binary RPMs: INLINECODE15
• Source RPM: INLINECODE16
• Build logs: INLINECODE17
• SPEC files: INLINECODE18

Security Notes

• - Build directory defaults to ~/rpmbuild to avoid conflicts with system-wide builds
• Builder identity is anonymized by default (uses OpenClaw Builder)
• No personal information is embedded in generated RPMs unless explicitly configured