When I update my local .cfg file, SimFactory does not see it and the files do not update. I'd like to see a regression test included in the fix of this bug.
This is the desired behaviour.
Often, people have several configurations with different option, or with options from previous versions of SimFactory. The most common use case is to keep an old version around because one does not yet trust the new version. In this case, SimFactory should not automatically modify the configuration.
The mental model is the following: Once a configuration has been configured, it should remain "stand-alone", independent of the changes that happen around it. This is similar to the way in which a simulation is self-consistent, containing e.g. a copy of the Cactus executable.
Since this topic has come up in the past, we should discuss the desired behaviour on the mailing list.
I agree with this in case the thornlist was given on the command line. Here however, this is not intuitive. Simfactory could store the fact that the default (configured) optionlist was used, and use this to update when this was changed. How else would I tell simfactory to update the optionlist else than explicitly specifying the optionlist - something I wanted to avoid in the first place by specifying it as default?