Quote:
Originally Posted by jackie_w
... and it's likely to stay that way.
fw 4.16.x is very different from 4.15.x and many patches need a re-write if that is possible, which isn't guaranteed.
Based on some of davidfor's post fw 4.17.x is also very different from 4.16.x.
It's just not worth the effort (IMHO) busting a gut to get 4.16.x patched. Once 4.17.x arrives we'll see what can be done.
It will probably need effort from all patch creators. It's not clear how many of those are still active at MR. If there are any orphaned patches which no longer work they may need a new volunteer foster-parent before they can be resurrected - assuming resurrection is even possible.
I don't want to be a kill-joy it's just that expectations need to be realistic once 4.17.x arrives.
|
For the impatient, all the nickel, rmsdk, and adobe patches have been updated and minimally tested. I'm not officially supporting them yet, so if you want them, you'll have to manually download them from GitHub. I haven't done libnickel or the new patches yet (I will soon do the ones I use, see my kobopatch config).
As for adopting patches, I'm planning to rewrite or deprecate Oren's patches, but most will be rewritten. The issue with them are they were just simple ports rewriting the whole stream, which isn't really feasible to update easily, and is quite fragile. I'm rewriting them to use the relatively new ReplaceZlibGroup instruction (it counters compression issues with many small replacements). I'm also adding comments and support for the newer language changes and a few device-related changes. For an example of this, see the rewritten kepub progress chart patch (it's now at the bottom of src/versions/4.16.13337/libnickel.so.1.0.0/geek1011.yaml).
As for the patches which will be deprecated or rewritten (so far), see src/version/4.16.13337/patches.md on GitHub.