When one builds a recipe featuring a Resources/Defaults/Settings directory, Compile will place those files under /Programs/Name/Version/Resources, and SymlinkProgram will take care of copying them over to /Programs/Name/Settings.
When a recipe does not include Resources/Defaults/Settings, however, "make install" will overwrite settings files from previous versions of the same package at /Programs/Name/Settings. It looks like the most sensible thing to do is to:
Let 'make install' copy settings files to /Programs/Name/Version/Resources/Defaults/Settings
Overwrite files at /P/N/V/Resources with a recursive copy of the recipe's default settings, if that exists
Invoke UpdateSettings through SymlinkProgram (we already do this)
This approach, at the very least, prevents problems with lost or missing settings files after the compilation of a frequently updated package.
hishamhm
commented
4 years ago
When one builds a recipe featuring a
Resources/Defaults/Settingsdirectory, Compile will place those files under/Programs/Name/Version/Resources, and SymlinkProgram will take care of copying them over to/Programs/Name/Settings.When a recipe does not include
Resources/Defaults/Settings, however, "make install" will overwrite settings files from previous versions of the same package at/Programs/Name/Settings. It looks like the most sensible thing to do is to:/Programs/Name/Version/Resources/Defaults/Settings/P/N/V/Resourceswith a recursive copy of the recipe's default settings, if that existsThis approach, at the very least, prevents problems with lost or missing settings files after the compilation of a frequently updated package.