Quote:
Originally Posted by pghaworth
that main kobopatch.yaml file can be customized too, right? I guess you could keep a modified yaml and just overlay the important info each time too, right? does the kobopatch.yaml stay the same each time or does it change?
|
There's no "One True Way". geek1011 has provided various options. Do what suits you best.
My kobopatch.yaml is used as Mission Control and gets used as-is from fw to fw. The only things that get changed (
except when I'm doing beta testing) are:
- the 2 occurrences of firmware number up at the top
- when I want to add a brand new patch to my list of enabled patches.
- when I've decided to permanently disable a previously used patch
I never change
Enabled: no to
Enabled: yes in the other yaml files. All on/off control is done in kobopatch.yaml.
Some people like to keep a full list of all patches in their kobopatch.yaml but I prefer to restrict mine to just the ones I'm going to enable - mainly because there are already so many in there, without cluttering it up with ones I'm never going to use.