本文介绍了ClearCase:是否可以对配置规范本身进行版本控制?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有复杂的配置规范,该规范经常更改.是否可以对配置规范本身进行版本控制?

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

例如假设当前的配置规范为: 元素* CHECKEDOUT

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

虽然先前的配置规范是: 元素* CHECKEDOUT

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.

有可能吗?怎么样?

推荐答案

您可以对配置规范本身进行版本控制(通过 cleartool catcs -tag YourViewTag > aConfigSpecFile )(为了不干扰常规的版本控制)其他文件)

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)

这个想法是,您可以随时通过 cleartool setcs :

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

cleartool setcs -tag yourViewTag yourConfigSpecFile

要获取该配置规范的特定版本(因为它存储在自己的分支中),您可以使用cleartool get

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

这篇关于ClearCase:是否可以对配置规范本身进行版本控制?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-14 02:24