Quote:
Originally Posted by PeterT
I was thinking last night that it might be interesting if when you build the tgz file it could include a configuration file listing which patches/options had been selected, and store this config file in the devices .kobo directory or .adds/patches
|
This already happens!
Currently, a manifest is stored in the (hidden) .kobopatch-webui folder at the root of the drive if you use "Connect to my Kobo" via USB and patch your device.
The manifest contains information about the patches you last chose, and you can "re-apply" the patches that you chose before if you attempt to go through the flow again.
The NickelMenu flow works the same way (it also generates a manifest) and there's a logs folder in there too for everyone who wants to see exactly what the webapp did to their device.