[ET Trac] [Einstein Toolkit] #52: Ensure consistency between configurations on different systems

[Einstein Toolkit]

#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 bmundim):

 Answering Erik: yes, I do regularly build multiple configurations in the
 same source tree,
 specially due to the large memory footprint of a ET checkout. So I don't
 like to have more than
 two (development and release) Cactus trees. I wouldn't mind to map
 thornlist name to configuration
 names (as long as tab completion is implemented too, as Ian suggested),
 but I don't see the point on
 enforcing it. The user should be able to set a different configuration
 name based on the same
 thornlist name with some thorns swapped by their private counterparts, for
 example, like Frank
 described.

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/52#comment:4>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit