kobopatch - An improved patching system - Page 6

geek1011 · 07-09-2018, 03:16 PM

Sample patch: show all games in beta features

See https://www.mobileread.com/forums/sh...15#post3719317

Advantages over old-style one: way shorter, does not need to be updated to new versions, easily editable.

Terisa de morgan · 07-09-2018, 03:37 PM

Thank you, this looks nice. I'll check it on the weekend.

geek1011 · 07-09-2018, 03:51 PM

Quote:

Originally Posted by Terisa de morgan

Thank you, this looks nice. I'll check it on the weekend.

No problem! This will make updating patches so much easier. Also note that this feature won't be much use until oren64 ports his patches.

Now I going to see if I can find a way to also make the other patches version-agnostic. I'm also going to make a nice site with documentation for kobopatch and see what I can do about porting the other patches over.

Terisa de morgan · 07-09-2018, 03:56 PM

Quote:

Originally Posted by geek1011

No problem! This will make updating patches so much easier. Also note that this feature won't be much use until oren64 ports his patches.

I'm aware of that, but this can be useful. And, about patching, it's easy, and additional file and that's all.

Quote:

Originally Posted by geek1011

Now I going to see if I can find a way to also make the other patches version-agnostic. I'm also going to make a nice site with documentation for kobopatch and see what I can do about porting the other patches over.

Thank you.

jackie_w · 07-09-2018, 04:41 PM

@geek1011,

I'm still not sure I fully understand how to use FindZlib. Please could you expand your #boggleContainer example. As it stands it looks as if it's enabling the beta games on a single device, the Kobo mini. Or have I misunderstood?

A more typical zlib patch would change multiple occurrences of a single variable (one per Kobo model) or even multiple occurrences of multiple variables.

geek1011 · 07-09-2018, 05:18 PM

Quote:

Originally Posted by jackie_w

@geek1011,

I'm still not sure I fully understand how to use FindZlib. Please could you expand your #boggleContainer example. As it stands it looks as if it's enabling the beta games on a single device, the Kobo mini. Or have I misunderstood?

A more typical zlib patch would change multiple occurrences of a single variable (one per Kobo model) or even multiple occurrences of multiple variables.

FindZlib just finds the base address of the zlib stream containing a unique string. That stream so happens to contain only the code for displaying the games, so I can replace all false visibility properties to true.

Also, another thing you might want to know is that ReplaceZlib automatically minifies the CSS if it is required. To accomodate for this, FindZlib will not care about inconsequential spaces.

I've also ported another patch: https://www.mobileread.com/forums/sh...49&postcount=5

jackie_w · 07-09-2018, 06:00 PM

Quote:

Originally Posted by geek1011

FindZlib just finds the base address of the zlib stream containing a unique string. That stream so happens to contain only the code for displaying the games, so I can replace all false visibility properties to true.

I've also ported another patch: https://www.mobileread.com/forums/sh...49&postcount=5

Thanks, that's much better. Doubly so because that particular zlib patch is one that I originally created and have been keeping up-to-date. You just saved me a job!

Quote:

Originally Posted by geek1011

Also, another thing you might want to know is that ReplaceZlib automatically minifies the CSS if it is required. To accomodate for this, FindZlib will not care about inconsequential spaces.

That was going to be my next question. Well anticipated.

geek1011 · 07-09-2018, 06:31 PM

Quote:

Originally Posted by jackie_w

Thanks, that's much better. Doubly so because that particular zlib patch is one that I originally created and have been keeping up-to-date. You just saved me a job!

That was going to be my next question. Well anticipated.

Also, note that currently (I'll fix it in another version), each replace_zlib is done independently. This means if you have issues fitting what used to fit in, just put it all in one big replace_zlib. For an example, see https://www.mobileread.com/forums/sh...67&postcount=6

jcn363 · 07-10-2018, 06:07 AM

There is any chance to use something like

Code:

  src/hyph_es.dic: usr/local/Kobo/hyphenDicts/hyph_es.dic

in kobopatch.yaml to put a file into KoboRoot.tgz?
Good luck.

geek1011 · 07-10-2018, 04:24 PM

Quote:

Originally Posted by jcn363

There is any chance to use something like

Code:

  src/hyph_es.dic: usr/local/Kobo/hyphenDicts/hyph_es.dic

in kobopatch.yaml to put a file into KoboRoot.tgz?
Good luck.

Yep. That's planned within a version or two.

Also, I have released the first fully converted version of the patches with all of GeoffR and oren64's patches converted to use the new kobopatch features. It can be downloaded here. Please test it and tell me if there are any bugs or possible improvements I could make. A few facts: it is half the size of the same patches in the old format, about half of the patches have been made version independent, all zlib patches now use my zlib functions, and oren64's patches are now included.

In addition, if oren64, jcn363, GeoffR, jackie_w, or anyone else who maintains patches wants write access to the GitHub repository, PM me.

NiLuJe · 07-10-2018, 04:27 PM

Spitballing for people regularly adding extra files (and @geek1011):

Does a source: target config like what @jcn363 proposed makes more sense than simply being able to simply feed another KoboRoot and letting the patcher merge them?

(It's a minor tooling change on my end, so I'm not particular about the details. I kind of like the merge the tarballs approach because it seems like a bit less work for me, and can be re-used for complex things more easily, but really, both approach would work for me

).

Terisa de morgan · 07-10-2018, 04:32 PM

Merge tar requires having created them before (nice... well, more or less, in linux, not so much in other systems), while @jcn63's approach looks simpler to me.

Terisa de morgan · 07-10-2018, 04:35 PM

Quote:

Originally Posted by jcn363

There is any chance to use something like

Code:

  src/hyph_es.dic: usr/local/Kobo/hyphenDicts/hyph_es.dic

in kobopatch.yaml to put a file into KoboRoot.tgz?
Good luck.

BTW, now I remember I added an hyphen for en too, that I've forgotten in the last patch, thank you for this.

geek1011 · 07-10-2018, 04:40 PM

Quote:

Originally Posted by NiLuJe

Spitballing for people regularly adding extra files (and @geek1011):

Does a source: target config like what @jcn363 proposed makes more sense than simply being able to simply feed another KoboRoot and letting the patcher merge them?

(It's a minor tooling change on my end, so I'm not particular about the details. I kind of like the merge the tarballs approach because it seems like a bit less work for me, and can be re-used for complex things more easily, but really, both approach would work for me

).

For me, it is way easier to allow adding more files rather than merging tarballs. Have a look at this code to see how much easier it is for me.

Also, is there any additional kobopatch tooling you think would be useful for people and patchmakers to have? I'm already working on one to automatically make sure all patches successfully apply.

NiLuJe · 07-10-2018, 05:16 PM

@geek1011: Yeah, I *definitely* get that (plus, handling potential conflicts and duplicates, fun times!

).

OTOH, nothing comes to mind, no. My use-case for the patching step is usually patches + hyphens, so, yeah, that works ^^.

My merge the tarballs idea can probably be done the dumb way in like three tar commands in a shell script, so, err, moving along

.

@Terisa de morgan: That's indeed a very good point, too

.

07-09-2018, 03:16 PM	#76
geek1011 Wizard Posts: 2,736 Karma: 6990705 Join Date: May 2016 Location: Ontario, Canada Device: Kobo Mini, Aura Edition 2 v1, Clara HD	Sample patch: show all games in beta features See https://www.mobileread.com/forums/sh...15#post3719317 Advantages over old-style one: way shorter, does not need to be updated to new versions, easily editable. Last edited by geek1011; 07-09-2018 at 03:50 PM.

07-10-2018, 06:07 AM	#84
jcn363 absolute beginner Posts: 323 Karma: 1750999 Join Date: May 2017 Location: Go with the wind (43°19'17.7"N 2°00'19.4"W) Device: ka1	There is any chance to use something like Code: src/hyph_es.dic: usr/local/Kobo/hyphenDicts/hyph_es.dic in kobopatch.yaml to put a file into KoboRoot.tgz? Good luck.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
kobopatch - A new (WIP) patching system	geek1011	Kobo Developer's Corner	93	05-27-2018 03:04 PM
Patching H2O	Maillemom	Kobo Developer's Corner	8	10-19-2016 09:58 AM
Instructions for patching firmware 3.17.3	GeoffR	Kobo Developer's Corner	60	09-17-2015 05:35 PM
Instructions for patching firmware 3.8.0	GeoffR	Kobo Developer's Corner	92	10-22-2014 07:22 AM
how to clean more disk space in root file system to upgrade system	chinaet	iRex	1	12-18-2006 03:54 PM

07-09-2018, 03:37 PM	#77
Terisa de morgan Grand Sorcerer Posts: 6,234 Karma: 11768331 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	Thank you, this looks nice. I'll check it on the weekend.

07-09-2018, 04:41 PM	#80
jackie_w Grand Sorcerer Posts: 6,212 Karma: 16534894 Join Date: Sep 2009 Location: UK Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3	@geek1011, I'm still not sure I fully understand how to use FindZlib. Please could you expand your #boggleContainer example. As it stands it looks as if it's enabling the beta games on a single device, the Kobo mini. Or have I misunderstood? A more typical zlib patch would change multiple occurrences of a single variable (one per Kobo model) or even multiple occurrences of multiple variables.

07-10-2018, 04:27 PM	#86
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Spitballing for people regularly adding extra files (and @geek1011): Does a source: target config like what @jcn363 proposed makes more sense than simply being able to simply feed another KoboRoot and letting the patcher merge them? (It's a minor tooling change on my end, so I'm not particular about the details. I kind of like the merge the tarballs approach because it seems like a bit less work for me, and can be re-used for complex things more easily, but really, both approach would work for me ).

07-10-2018, 04:32 PM	#87
Terisa de morgan Grand Sorcerer Posts: 6,234 Karma: 11768331 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	Merge tar requires having created them before (nice... well, more or less, in linux, not so much in other systems), while @jcn63's approach looks simpler to me.

07-10-2018, 05:16 PM	#90
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@geek1011: Yeah, I definitely get that (plus, handling potential conflicts and duplicates, fun times! ). OTOH, nothing comes to mind, no. My use-case for the patching step is usually patches + hyphens, so, yeah, that works ^^. My merge the tarballs idea can probably be done the dumb way in like three tar commands in a shell script, so, err, moving along . @Terisa de morgan: That's indeed a very good point, too .

Advert

Advert