Quote:
Originally Posted by geek1011
Mine is not meant to be equivalent, it is meant to be more. So far (except for this version, but probably not too many others), GeoffR has been updating the patches (either in the new or the old format), and I have been adding them to kobopatch. One is usually the source of truth for the patches.
As for the zlib patches, since kobopatch makes it WAY easier to maintain them, I can write a converter to the old format if anyone wants it.
The thing is, I've designed kobopatch so it can be as complex or as simple as you need it. If you only want the basics (like the old version), you can modify the patch files directly and ignore kobopatch.yaml. The new syntax should be pretty simple to pick up. I'm also willing to add anything to make it simpler (if it even can be made simpler). Some of my future plans include: automatic firmware downloading, an automated patch removal tool, optional automated installation, and if I can get it to work (I've been unsucessful so far), a virtual kobo in QEMU.
|
No need to be so defensive, geek1011, my problem is not with the new system, which I like a lot, not least because of its improvements in patching the nickel file.
My problem is that if people are reluctant to
even try to move forward to the new system "because the old works just fine" (
and I agree, it does work fine and I've been very grateful for it for several years) then we will forever have 2 systems. I get it that, on the whole, people hate change but I'm sceptical that keeping 2 systems in-sync is workable in the long run (
BTW, I'm happy to be proved wrong 
)
For the record, any future contributions from me will be for kobopatch in .yaml format. If someone else wants to translate them to .patch format and do the testing that's perfectly OK by me.