========================================== NOTES FOR PACKAGING FEDORA-RELEASE-NOTES ========================================== If you want to turn the current release notes into a SRPM package for import to Core, do the following: SHORT VERSION -------------- #/bin/bash cd /build/dir export CVSROOT=:pserver:anonymous@cvs.fedoraproject.org:/cvs/docs cvs co docs-common release-notes about-fedora homepage readme readme-burning-isos for i in about-fedora homepage readme* ; do pushd $i/devel make release-pkg && cp *.tar.gz ../../release-notes/devel/ popd done cd release-notes/devel/ make release-srpm LONG VERSION ------------- 1. Make sure you have the following modules at the same tree depth. These are all found in Docs CVS. * release-notes/ * docs-common/ SUPPLEMENTALS: * about-fedora/ * homepage/ * readme/ * readme-burning-isos/ 2. In each module in the "SUPPLEMENTAL" list, do "make release-pkg". This builds a tarball for use in the release-notes SRPM. Copy the tarball to the release-notes/devel/ folder. *Make sure the release number of the tarball matches that for the release-notes!* 3. Edit the fedora-release-notes.spec file, edit the "Release" tag and make a new entry in the %changelog. There is no need to use %{?dist} since this is a single-release package. 4. Run 'make release-srpm' to build the SRPM. The contents of the source tarball -- the ones not already in the top-level directory -- remain in the "fedora-release-notes-<version>/" directory if you want to review them. The tarball is there as well. -- PWF, rev. 27 Jan 2007