I understand the .conf script to be for building new Patches... I am wondering thoughts on how to "move" patches from TKL Generations to new ones.
If one builds, say a 11.1 Patch, then applies the same patch to 11.2 or 11.3 or perhaps 11.3 then runs a TKLBAM Restore will the full old Dataset also move forward?
I ask because I would like to be building more patches for my own use but worrry about getting them stranded when the systems update generationally.
Also, as I noted in a different post/comment: Is there a way to load a "Patched ISO" to the TKL Hub? Would seem to speed the testing process.
Patches and Upgrades.
Rik et al:
I understand the .conf script to be for building new Patches... I am wondering thoughts on how to "move" patches from TKL Generations to new ones.
If one builds, say a 11.1 Patch, then applies the same patch to 11.2 or 11.3 or perhaps 11.3 then runs a TKLBAM Restore will the full old Dataset also move forward?
I ask because I would like to be building more patches for my own use but worrry about getting them stranded when the systems update generationally.
Also, as I noted in a different post/comment: Is there a way to load a "Patched ISO" to the TKL Hub? Would seem to speed the testing process.
thanks for your work here and elsewhere.