#52: Ensure consistency between configurations on different systems --------------------------+------------------------------------------------- Reporter: anonymous | Owner: mthomas Type: enhancement | Status: new Priority: minor | Milestone: Component: SimFactory | Version: Resolution: | Keywords: --------------------------+-------------------------------------------------

Comment (by knarf):

I don't think this is a good idea. In part, because it goes against my usual practice. I usually call configurations simply 'sim' out of convenience and often have several complete checkouts for different configurations - often because I do have different versions of the same thorn, or would like to update some thorns for one configuration but not another. I would not be interested in a simulation name similar to the thornlist name. Just for the record: yes, I do usually use the same thornlist for the same checkout and configuration name. I just don't see the need to enforce that.

This ticket is already quite old. If there is no other opinion within a week or so, I will probably close it - because it is also not known who actually submitted it.