2 ms·
> The core problem is you're having people modify files that you will also change, for example when you release a new version of your software that has new opti
by kazinator 3y ago
> The core problem is you're having people modify files that you will also change, for example when you release a new version of your software that has new options that you want people to be able to change or configure.
That's a solved problem. You have an "example-config.xyz" file in the distribution that the user must rename to "config.xyz" and customize.
The new version of the software clobbers example-config.xyz, not touching config.xyz.
If the user also retains the original example-config.xyz in a copy called ORIG-config.xyz, then after the upgrade, they can do a three-way diff.
- jraph 3y agoYep. As an alternative, make your program work with a default set of configurations (that can be in a file shipped with the app) and let the user only specify the changes they want. This way, the tree way diff is not necessary anymore in most cases.