2

I have complicated Config Spec, which changes quite often. Is it possible to version control the config spec itself?

e.g., suppose the current config spec is: element * CHECKEDOUT

element /vobs/a/b/c.v  /main/34
element /vobs/a/d/e.v  /main/20
element /vobs/f/g.f LABEL_0.592
element /vobs/... LABEL_0.596

While the previous config spec was: element * CHECKEDOUT

element /vobs/h/i/j.v  /main/31
element /vobs/... LABEL_0.595

I'd like to be able to "go back" to my previous config spec, without having to keep it in comments inside the config spec, or copy-paste it every time to seperate file, and have that file version controlled.

Is it possible? How?

Zvika
  • 1,542
  • 2
  • 17
  • 21

1 Answers1

1

You could version the config spec itself (obtained with cleartool catcs -tag YourViewTag > aConfigSpecFile) in its own branch (in order to not interfere with the regular versioning of the other files)

The idea is that you can set a config spec from a file at any time, with cleartool setcs:

cleartool setcs -tag yourViewTag yourConfigSpecFile

To get a specific version of that config spec (since it is stored in its own branch), you can use cleartool get

cleartool get –to yourConfigSpec yourConfigSpec@@\main\aBranch\x
Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • That's what I've started to write here... you're the first one vonc :) @zvika - you can use cleartool catcs > filename to save the config spec – Tamir Gefen Jun 02 '14 at 08:58
  • @Vonc - using `ct setcs -f` is a great solution. Googling added the info that I should also use `ct setcs -cur` to refresh the CS every time it's changed. Thanks! – Zvika Jun 02 '14 at 09:32
  • @TamirGefen - Good to hear from you. If I'm not mistaken, we learnt together in Eli... – Zvika Jun 02 '14 at 09:33
  • @Zvika I have edited the answer (there is no -f option), added links to the documentation and added how to get a specific version. – VonC Jun 02 '14 at 09:35