From Fedora Project Wiki

(Created page with '== 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...')
 
 
(21 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 ==
git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git spin-kickstarts
 
cd spin-kickstarts
* Get a checkout of the appropriate spin-kickstarts branch
# If you need a specific branch other than master:
** <code>git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git spin-kickstarts</code>
git checkout BRANCHNAME
** <code>cd spin-kickstarts</code>
# Edit configure.ac to update the version or release
* If not using the master branch switch to the appropriate branch
# Edit spin-kickstarts.spec.in to update the change log
** <code>git checkout BRANCH_NAME</code>
aclocal
* Make a new spin-kickstarts tar ball
automake
** <code>git tag 0.X.Y</code> (where X is the Fedora version and Y is a sequence number)
autoconf
** <code>git push --tags</code>
./configure
** <code>make</code>
make dist
* Publish the tar ball
install -D -m 644 spin-kickstarts-*.tar.gz ~/rpmbuild/SOURCES
** <code>make publish</code>
# Edit spin-kickstarts.spec if some changelog history needs to be included
* To make a new package of spin-kickstarts for a Fedora branch:
install -D -m 644 spin-kickstarts.spec ~/rpmbuild/SPECS
** Go to the local branch directory for the spin-kickstarts package (perhaps after running <code>fedpkg clone spin-kickstarts</code> in an appropriate directory).
rpmbuild -ba ~/rpmbuild/SPECS/spin-kickstarts.spec
** Make sure the branch is up to date
# If the sprm gets published then publish the tar.gz file on fedorahosted
*** <code>git pull</code>
scp spin-kickstarts-*.tar.gz fedorahosted.org:spin-kickstarts
** Update the tar archive using the one built above
# Clean up the generated files:
*** <code>fedpkg new-sources /pathto/spin-kickstarts-*.tar.gz</code>
git clean
** Edit the spec file for the version tagged and to add a changelog entry
# To update a branch of spin-kickstarts
** Commit the changes
Make sure the branch is current (cvs up)
*** <code>git commit -a</code>
#  Copy over the new spec file
*** <code>git push</code>
#  In each branch run make new-sources FILES=/pathto/spin-kickstarts-*.tar.gz
** Build the update
Commit the changes with cvs commit
*** <code>fedpkg build</code>
#  Make a new tag with make tag
** 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.
#  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.