Hi guys! I was thinking in releasing a TKLPatch for TKLPatch Development. :) It consists of Turnkey Core+tklpatch installed+Turnkey Core image inside by default. Maybe son helper scripts to create the basic tklpatch structure and the helper functions (install, cleanup_apt).
I also thought of using apt-cacher (mentioned by Jed in other thread) to create a "deb cache" for the appliances, so that if you have a slow connection, once you've downloaded apache for the first patch, the next ones will use the cached deb. The only thing that stops me on this is telling tklpatch-chroot to change source apt repos to localhost and set the originals on exit. It may be a function for conf, but then it won't be a default behaviour.
Also, a shared folder for output (or an ftp server by default) will leave your isos ready to get them (I usually scp them but to make it easier for newcomers to take the results "out of there!")
What do you think of this idea? This would help other people to apply TKLPatchs as the only need to install the Dev Env appliance. And the apt-cache will help developers speed up their work.
I'll work on it when I finish the ones I'm making, in the meantime feedback is welcome.
P.S: Looking into the feature you can even have a webmin module to apply patches :D maybe it reads an online approved official TKLPatchs lists with info about the base used (if not turnkey core) and automatically donwload the base (to the turnkey base images folder) and apply the patch, leaving it in the patched iso's folder (with a nice name set in the info file too, so that you don't end up with tkl-patched file).