From Fedora Project Wiki

No edit summary
 
(19 intermediate revisions by the same user not shown)
Line 1: Line 1:
== When ==
== 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 if there was a change shortly after a release. When spin-kickstarts is branched for a release, a new devel package should be built corresponding to the next Fedora release.
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 ==
== How ==
Line 7: Line 7:
* Get a checkout of the appropriate spin-kickstarts branch
* Get a checkout of the appropriate spin-kickstarts branch
** <code>git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git spin-kickstarts</code>
** <code>git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git spin-kickstarts</code>
** <code>cd spin-kickstarts<code>
** <code>cd spin-kickstarts</code>
** If not using the master branch switch to the appropriate branch
* If not using the master branch switch to the appropriate branch
*** <code>git checkout BRANCH_NAME</code>
** <code>git checkout BRANCH_NAME</code>
** If there is new, removed or moved kickstart file update Makefile.am to reflect that.
* Make a new spin-kickstarts tar ball
** Edit configure.ac to update the version or release
** <code>git tag 0.X.Y</code> (where X is the Fedora version and Y is a sequence number)
** Edit spin-kickstarts.spec.in to update the change log
** <code>git push --tags</code>
** If any changes above have been made, then they should be committed and pushed back
** <code>make</code>
* Publish the tar ball
** <code>make publish</code>
* To make a new package of spin-kickstarts for a Fedora branch:
** Go to the local branch directory for the spin-kickstarts package (perhaps after running <code>fedpkg clone spin-kickstarts</code> in an appropriate directory).
** Make sure the branch is up to date
*** <code>git pull</code>
** Update the tar archive using the one built above
*** <code>fedpkg new-sources /pathto/spin-kickstarts-*.tar.gz</code>
** Edit the spec file for the version tagged and to add a changelog entry
** Commit the changes
*** <code>git commit -a</code>
*** <code>git commit -a</code>
*** <code>git push</code>
*** <code>git push</code>
** <code>aclocal</code>
** Build the update
** <code>automake</code>
*** <code>fedpkg build</code>
** <code>autoconf</code>
** 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.
** <code>./configure</code>
** <code>make dist</code>
install -D -m 644 spin-kickstarts-*.tar.gz ~/rpmbuild/SOURCES
# Edit spin-kickstarts.spec if some changelog history needs to be included
install -D -m 644 spin-kickstarts.spec ~/rpmbuild/SPECS
rpmbuild -ba ~/rpmbuild/SPECS/spin-kickstarts.spec
# If the sprm gets published then publish the tar.gz file on fedorahosted
scp spin-kickstarts-*.tar.gz fedorahosted.org:spin-kickstarts
# Clean up the generated files:
git clean
# To update a branch of spin-kickstarts
#  Make sure the branch is current (cvs up)
#  Copy over the new spec file
#  In each branch run make new-sources FILES=/pathto/spin-kickstarts-*.tar.gz
#  Commit the changes with cvs commit
#  Make a new tag with make tag
#  Do the build with make build

Latest revision as of 19:15, 29 June 2013

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
    • git checkout BRANCH_NAME
  • Make a new spin-kickstarts tar ball
    • git tag 0.X.Y (where X is the Fedora version and Y is a sequence number)
    • git push --tags
    • make
  • Publish the tar ball
    • make publish
  • To make a new package of spin-kickstarts for a Fedora branch:
    • Go to the local branch directory for the spin-kickstarts package (perhaps after running fedpkg clone spin-kickstarts in an appropriate directory).
    • Make sure the branch is up to date
      • git pull
    • Update the tar archive using the one built above
      • fedpkg new-sources /pathto/spin-kickstarts-*.tar.gz
    • Edit the spec file for the version tagged and to add a changelog entry
    • Commit the changes
      • git commit -a
      • git push
    • Build the update
      • fedpkg build
    • 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.