How do you manage your patches to Gramps? I am looking for practical ideas for keeping a logbook of how to reconfigure a fresh install.
I have a bunch of patches installed manually into my Gramps 5.1.2 version. Some are 5.2 targeted patches. Some are ‘fork’ patches that will never make it into the main product. So when 5.1.3 is released, I’ll lose them and have to repatch.
Likewise, when 5.1.3 comes out or it becomes necessary to re-import an XML backup in order to repair a corrupted database, important configuration customizations can be lost.
I’ve become aware that some Preferences are stored in the Tree (like when you change the ID format to have more leading zeroes), some are in .ini files in the application folder & some are in the user writable (%AppData% on a PC) space also for add-ons. How do you keep track of which are persistent across all Trees & which are Tree specific?
How do you keep track what has to be reset on each re-install or fresh import restore? Some are merely inconvenient but others would result in data loss or inconsistency.