Quote:
Originally Posted by npr
It's really not that difficult to understand, my main problem was entering the list of patches with the yes / no flag and the inevitable typos I made which stopped the patching process and needed correcting.
The second issue I had was when I ran the new patch using the kobopatch.yaml from the previous patch version. The patching process stopped at every missing patch even though they were flagged as "no", it then took some time to identify the missing patch and remove it from the .yaml file.
One solution would be to only list "patch name: yes" in the .yalm file
Alternatively what do you think about making missing "no" patches have a soft fail. I don't see why the patch process needs to stop when a "no" patch is missing.
|
Thanks for the feedback! For making patch selection easier, what do you think of a web interface to generate kobopatch.yaml easier?
For the overrides, you only need to list the yes ones, as all patches are disabled by default. Your last suggestion sounds good though. I'll do it for the next version.