Building RPMs

See building RPMs for Fedora

Special notes for TigerOS

• Packages that do not replace upstream Fedora version should install into /usr/local/bin or an appropriate directory in accordance with the FHS.
• Packages that do replace the upstream Fedora version should include a conflicts and an obsoletes statement for the Fedora package it replaces. All packages that replace upstream versions should be tested to ensure compatibility.

Typical workflow for creating a new TigerOS specific package

1. Get sources
2. Write spec file
3. Create source tarball (naming of directories MUST match the spec file, usually packagename-version)
4. Run fedpkg --release [fedora release in the form f[number]] mockbuild in the directory with the tarball and spec
5. Add the SRPM to the staging area, notify admin that package is ready
6. Once admin notifies you that the package has been signed and the repo updated, download the new SRPM and add it to git

Typical workflow for updating existing TigerOS specific packages

1. rpmdev-extract existing SRPM and edit.
   1. Also edit raw sources in git if applicable
   2. Add changed raw sources to git
2. Edit specfile for new version and add changelog entry(alternatively use rpmdev-bumpspec)
3. Recreate source tarball
4. Run fedpkg --release [fedora release in the form f[number]] mockbuild in the directory with the tarball and spec
5. Add the SRPM to the staging area, notify admin that package is ready
6. Once admin notifies you that the package has been signed and the repo updated, download the new SRPM and add it to git