ClearCase: Is it possible to version control the config spec itself?

280 views Asked by At

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?

1

There are 1 answers

4
VonC On

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