Quote:
|
Originally Posted by Ripplinger
I guess I'm not seeing how any of that can be automated.
|
Maybe the name is poorly chosen; it's not supposed to automate the editing of patches at all, that part will always have to be done manually I guess. It just performs the patching itself, given the patchfiles. So it only replaces the step that's currently done on the computer (downloading firmware, executing some script, putting the resulting KoboRoot.tgz on the reader).
Quote:
Originally Posted by GeoffR
What happens when the firmware is updated, does the autopatcher need to be re-installed?
|
No; it currently only adds files to the firmware, without modifying any existing ones, so nothing is overwritten by an update. Until you do a factory reset...
Quote:
Originally Posted by GeoffR
Does it handle the situation where a firmware update only changes some files and not others?
|
It uses checksums to keep track of things. It will try to (re)apply patches whenever the checksum (of either files or patches) changes. If someone uses KoboRoot.tgz to replace only one file, then it would be patched again.
Quote:
Originally Posted by GeoffR
From what I understand the device needs to reboot twice after changing a patch to install the new patch?
|
Yes, but only because it's not hooked into USB yet. The final version should react to changed patchfiles the same way it does to putting KoboRoot.tgz on it and patch/reboot the device only once.
Quote:
Originally Posted by GeoffR
For those already used to patching from an external computer there probably isn't any incentive to switch to this method, but perhaps those who haven't patched before will find this method easier.
|
It also opens up to new possibilities, like a patch [Yes/No] selection screen on the device itself. (Although that's beyond my ability at this point)
It already supports several patch files, so if you were to split the one big file into individual ones, you'd no longer have to edit just for [Yes/No], you could just move the ones you don't want into the disabled dir.
I still want to add support for patches that work for any firmware version as long as its unique signature can be found; so while a string may be at a different address in each firmware version, as long as it's the same string and unique the patch should still work.