Rebuilding Spins Packages

When
This package should get rebuilt shortly before alpha, beta and the release, when there have been changes in spin kickstart files since the last build. An update should be done shortly after a release, if there was a change to the release branch of spin-kickstarts since the last build. When spin-kickstarts (git repo) is branched for a release, a new devel package should be built corresponding to the next Fedora release.

How

 * Get a checkout of the appropriate spin-kickstarts branch
 * If not using the master branch switch to the appropriate branch
 * If there is new, removed or moved kickstart file update Makefile.am to reflect that.
 * Also note that if a kickstart file is moved from the top directory to one of the subdirectories (e.g. custom), any includes done by the kickstart file need to prefix   to the include file names.
 * Edit configure.ac to update the version or release
 * Edit spin-kickstarts.spec.in to update the change log
 * You normally want to look at the spec file currently used in the package and copy new stuff back from it.
 * If any changes above have been made, then they should be committed and pushed back
 * Edit spin-kickstarts.spec if some changelog history needs to be included from existing package, that isn't in the changelog in the git repo. (And isn't wanted there; otherwise it should have been done above.)
 * To make a local srpm (perhaps for testing):
 * To make a new package of spin-kickstarts for a Fedora branch:
 * Go to the local branch directory
 * Make sure the branch is up to date
 * Copy over the new spec file
 * Update the tar archive using the one built above
 * Commit the changes
 * Build the update
 * If this isn't the devel branch go to bodhi and push the release out to testing initially and updates later if there are no problems.
 * The spin-kickstarts tar.gz file should get posted on the spin-kickstarts fedorahosted page.
 * To clean files created by the build process out of the git directory
 * To make a new package of spin-kickstarts for a Fedora branch:
 * Go to the local branch directory
 * Make sure the branch is up to date
 * Copy over the new spec file
 * Update the tar archive using the one built above
 * Commit the changes
 * Build the update
 * If this isn't the devel branch go to bodhi and push the release out to testing initially and updates later if there are no problems.
 * The spin-kickstarts tar.gz file should get posted on the spin-kickstarts fedorahosted page.
 * To clean files created by the build process out of the git directory
 * Commit the changes
 * Build the update
 * If this isn't the devel branch go to bodhi and push the release out to testing initially and updates later if there are no problems.
 * The spin-kickstarts tar.gz file should get posted on the spin-kickstarts fedorahosted page.
 * To clean files created by the build process out of the git directory
 * If this isn't the devel branch go to bodhi and push the release out to testing initially and updates later if there are no problems.
 * The spin-kickstarts tar.gz file should get posted on the spin-kickstarts fedorahosted page.
 * To clean files created by the build process out of the git directory
 * To clean files created by the build process out of the git directory