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.

NOTE: By running yum inside the chroot you may mess up the rpmdb version, this depends on how close your host system is to the target system. So YMMV

Build with a test anaconda.rpm

NOTE: This doesn't actually seem to work when the released anaconda version matches that in the branch. buildinstall isn't letting the local repo override the one in the repo

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)

make sure mock is mounting your anaconda directory as described above. Again, do not use mount -o bind to do it.

mock -v -r fedora-13-i386-proxy --shell

cd /root/anaconda

Removed the cached files. Otherwise it pull pull from there and not update to the latest