Actually there is usually no need to fiddle with the configuration directory when using Syncthing from different sources. The compiled binary is always the same. Just in case one version is newer and it brings a new config file format, then the config file is upgraded after making a backup copy automatically. Thus you can always return to the older version by renaming that backup to config.xml again, or by using the --allow-newer-config command line switch.
Thank you for this information I will make a note of it and the switch too.
I don’t think this was known and these switches were not used and alternating versions were executed.
The compiled binary is always the same.
Actually there are two distinctly different versions of the binary file. 1.23.7 and 1.24.0.
My suggestion was based upon my own past experience having installed two different versions that were not compatible with each other because one came from an outdated software repository and the other came from the website download area.
I was hoping that if this person deleted one of the two installations, the older one and also the configuration directory and only ran the new software it would create a new config file and everything would be happy.
I don’t ever use RPM distros so I know nothing about how to manipulate their packaging.