是“再循环”吗？一个没有副作用的ClearCase动态视图，如果没有，如何重命名视图？
我工作的一家商店依赖于 ClearCase 中的动态视图。既定的规范是为每个项目工作创建一个新的视图。随着时间的推移，我发现我只需要同时激活一两个视图。我已经通过更改配置规范来“重用”视图（在签入、标签、发布等之后）。到目前为止，事情已经解决了。这样做有什么长期问题吗？如果没有，我是否可以重新命名视图（更改视图标签）以更好地反映视图的用途？
One of the shops I'm working at relies on dynamic views in ClearCase. The established norm has been to create a new view for each project effort. Over time I've found that I've only needed to have one or two views concurrently active. I've taken to "reusing" a view by changing the config spec (subsequent to check-in, label, release, etc.). So far, it has worked out. Is there any long-term problem with doing that? If not, is there anyway I can re-name the view (change the view tag) to better reflect what the purpose of the view is?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
对于基本 ClearCase 动态视图，回收配置规范时唯一的副作用是私有文件：
这些存储在动态视图存储中，并且在重置配置规范时并不总是被删除。
您还需要确保没有文件被签出：它们也存储在视图存储中，一旦配置规范发生更改，它们可能不再可见/不可访问（但您仍然应该能够取消它们）通过“查找合作”GUI）。
您无法重命名（更改标签）视图（动态或快照），
而且，为了完整起见，您无法回收UCM动态视图（引用流）的配置规范。
您可以尝试更改所述流的基础基线，但同样，这并不总是可行。
For base ClearCase dynamic views, the only side-effect you can have when recycling a config spec are private files:
Those are store within the dynamic view storage, and not always removed when the config spec is reset.
You also need to make sure no files were left checked-out: they also are stored in the view storage, and once the config spec has changed, they may not be visible/reachable any more (but you should still be able to unco them through the 'find co' GUI).
You cannot rename (change the tag) of a view (dynamic or snapshot)
And, just to be complete, you cannot recycle the config spec of an UCM dynamic view (which reference a stream).
You can try to change the foundation baselines of said stream, but again, that is not always possible.
我投票赞成废除旧观点并重新创建观点。除了 VonC 的所有出色输入之外，从磁盘空间的角度来看，旧视图往往会随着时间的推移而变得庞大，很快您就不会成为系统管理员的最爱:-)
I vote for scrapping old views and creating views afresh. Besides all teh great inputs from VonC, from the disk space point of view, old views tend to get bulky over time and you soon you wont be a favorite with your sysadmins :-)
根据我的经验，仅使用 2 个动态视图而不是每个“项目”使用一个动态视图不会产生对数术语影响。如果您不需要同时活动视图，这是一个很好的方法，如果动态视图可以非常快速且频繁地更新，那就太好了。
对于重命名部分，为什么要重命名呢？制作一个类似的新动态视图（或两个）并为其指定一个新名称（视图标签）。
From my experience there is no log term affect for using only 2 dynamic views instead of one for each "project". If you don't need the views active concurrently its a good method, thats the beauty if dynamic views they can be updated very fast and very frequently.
For the renaming part, why rename? make a similar new dynamic view (or two) and give it a new name (view tag).