Instructions for patching firmware 4.10.11591 - Page 6

Terisa de morgan · 08-29-2018, 01:31 PM

Another question: Is there any way to set the release as an environment variable, a parameter, or something like that? So, I will have to edit nothing in the configuration file from a release to other.

Mrs_Often · 08-29-2018, 03:04 PM

Quote:

Originally Posted by oren64

Just to be clear, I highly recommend the new system kobopatch, although I didn't install FW 4.10.11591 (no mark 4).

Here are the advantages of kobopatch as I see them:

1) Folding all patches, seeing all the patches in a small area (notepad++ Alt+0)

2) Patching directly CSS streams, have the ability to edit patches in nickel.ymal file like `New home screen increasing cover size` patch.

3) Saving patches enable options in configuration file kobopatch.ymal so you can use it in the next firmware.

4) Separating custom patches from the included ones, let say you want to enable the patch `Custom reading footer style` but you don't want to edit it every firmware, add a ymal file (name like my_nickel.ymal) to src folder and copy the patch to it and edit, copy the file to next firmware folder.
Edit:You need to set the file in kobopatch.ymal.

Thank you for that! It confirms only vague insecure suspicions of what is possible. I had no idea about 4 (didn't understand any of the "src talk" I previously read), that's a nice function!

Terisa de morgan · 08-29-2018, 03:32 PM

Quote:

Originally Posted by Mrs_Often

Thank you for that! It confirms only vague insecure suspicions of what is possible. I had no idea about 4 (didn't understand any of the "src talk" I previously read), that's a nice function!

The fourth point was very useful for me in the previous firmware.

boriar · 08-29-2018, 03:42 PM

Quote:

Originally Posted by Terisa de morgan

The fourth point was very useful for me in the previous firmware.

I suppose that this option is only valid with a multi-version patch, isn't it?

Terisa de morgan · 08-29-2018, 03:49 PM

Quote:

Originally Posted by boriar

I suppose that this option is only valid with a multi-version patch, isn't it?

Yes and no, I had two different patches for nickel: the "standard" and another with the patches by oren64, and I think it's not related with multiversion although it could be the most logical use.

boriar · 08-29-2018, 04:21 PM

Good point!
I think that kobopatch let organize the patch in the best way for anyone.

I use the new patch system from 4.8.xxxx but the more I use it the most I like.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Instructions for patching firmware 3.13.1	GeoffR	Kobo Developer's Corner	56	07-01-2016 09:59 AM
Instructions for patching firmware 3.16.10	GeoffR	Kobo Developer's Corner	12	08-14-2015 03:40 AM
Instructions for patching firmware 3.11.0	GeoffR	Kobo Developer's Corner	226	06-01-2015 05:32 AM
Instructions for patching firmware 3.12.1	GeoffR	Kobo Developer's Corner	56	03-20-2015 05:14 AM
Instructions for patching firmware 3.2.0	DNSB	Kobo Developer's Corner	66	12-05-2014 07:28 AM

08-29-2018, 01:31 PM	#76
Terisa de morgan Grand Sorcerer Posts: 6,233 Karma: 11768331 Join Date: Jun 2009 Location: Madrid, Spain Device: Kobo Clara/Aura One/Forma,XiaoMI 5, iPad, Huawei MediaPad, YotaPhone 2	Another question: Is there any way to set the release as an environment variable, a parameter, or something like that? So, I will have to edit nothing in the configuration file from a release to other.

08-29-2018, 04:21 PM	#81
boriar Evangelist Posts: 407 Karma: 314204 Join Date: Jan 2015 Device: bq Avant XL, Kobo Aura H2O, Onyx Boox M96C Plus	Good point! I think that kobopatch let organize the patch in the best way for anyone. I use the new patch system from 4.8.xxxx but the more I use it the most I like.