View Single Post
Old 07-17-2019, 05:06 PM   #292
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,808
Karma: 7423683
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by lbschenkel View Post
Hi geek1011, I have a suggestion: could the overrides in the main yaml file be moved or included from a separate file, so when upgrading firmwares and patches all we need to do is to copy that override file across versions without touching anything else? That would be a great usability improvement.

I mean something like this in kobopatch.yaml:
Code:
overrides_file: overrides.yaml
overrides.yaml:
Code:
src/nickel.yaml:
  Patch 1: yes
  Patch 2: yes
src/libadobe.so.yaml:
  Patch 3: yes
  Patch 4: yes
...
Not sure if there's a lot of value to allow arbitrarily specifying a file name, you might as well just look for a specifically-named file such as overrides.yaml. You can keep the existing override mechanism so it doesn't break existing setups and additionally use this file.

What do you think?
I decided to put it in kobopatch.yaml so people wouldn't blindly update. The main reason for this is you already need to install the firmware first, and funny things happen if you forget to. I've discussed the rest of the reasoning behind this in other posts as well.
geek1011 is offline   Reply With Quote