How to Cook A GoOSe

The following is an explanation of what it takes to rebuild enterprise Linux. In the case of the GoOSe Project, our goal is to rebuild an enterprise release from a popular upstream vendor.

1. Get the upstream target package (binary RPMs) list.

Currently provided by spacewalk-remote-utils from http://spacewalk.redhat.com/yum/. (The future seems to be http://git.centos.org)

2. Get SRPMs needed to generate target package list
3. mkdir pkg && cd pkg
4. git init && touch .gitignore sources && git add .gitignore sources
5. git commit -m "Initial setup of the pre-review repo"
6. git checkout -b upstreamver (where upstreamver is something like el6.0)
7. goosepkg import pkg-0.1-1.el6.src.rpm
8. git commit -m "initial import of pkg-0.1-1.el6.src.rpm"
9. git checkout -b gl6.0 (or whatever matches the koji tag)
10. goosepkg upload <sourcefiles>
11. git add . && git commit -m "some crazy message" && git push
12. goosepkg build --nowait, which does

• create mock chroot
  • git checkout from github repo
    • make sources
      • this fetches the tarball from lookaside cache and compares sha256sum
    • rpmbuild of SRPM
  • new mock chroot
    • rpmbuild of RPMs
  • tag the new build in koji system

Here we end up with a bunch of packages.

• targets in koji (packages and stuff needed for build steps)
• tags in koji (packages from output of koji builds)

13. Sign packages using `sigul`
14. Organize Stuff

• Convert packages in koji into yum repos based on tags. Results in 'everything' repo eg /goose/ repo. We use mash.
• /Updates/ repo will be done the same way.

15. Compose ISO images using `pungi`

Here we end up with iso images and install trees.

16. QA stuff

• lots of handwavy autotest/autoQA
• automate kickstart installs via rat_install? http://kparal.wordpress.com/2012/03/16/autoqa-0-8-released/

17. Release management

• Mirror management mirrormanager
• mailing list announcements
• twitter/fb/website announce
• lifecycle management