Building updates

Anaconda includes the ability to update itself by passing updates=http://path/to/update.img to the kernel at boot time. This allows you to use the same boot media and test changes to stage2 of the installer.

This assumes a working mock chroot (ie. I built boot images with this one first)

You need a git repo of Anaconda, I branch for the build so I don't clutter up master with build by-products.

Build with a test anaconda.rpm

Normally when a punji build is done it pulls anaconda from the repo/proxy cache. Instead you want it to use your new build (ie. when doing stage1 development which cannot be updated by updates= being passed to the kernel)