| 1. | The binary files will not be checked in to the vob 二进制文件将不能检入到版本对象库( vob ) 。 |
| 2. | What vobs are using what triggers 哪些vob使用的哪些触发器? |
| 3. | You will probably continue to use the same vob structure that is in your current system 你有可能在你当前的系统里继续使用相同的vob结构。 |
| 4. | I like the latter approach for creating vob containers that store similar types of artifacts 我倾向于后者来建立存储相似类型工件的vob容器。 |
| 5. | In a production environment the tivoli framework server will be separate from the clearcase vob server 在生产环境下, tivoli框架服务器将与clearcase vob服务器分离。 |
| 6. | Chances are you probably have been using directories in your vob as a folder of some sort in base clearcase 你可能在你的vob中一直在使用目录作为base clearcase中的某些对象种类的一个文件夹。 |
| 7. | However , a component cannot span multiple vobs , and the largest a component can be is the size of its vob 然而,一个构件不能跨越多个版本对象库( vob ) ,最大的构件大小就是它的版本对象库( vob ) 。 |
| 8. | A model vob container can store multiple model components ; a deployment vob container can store multiple components of deployable assets 模型vob容器能够存储多模型组件;部署vob容器能够存储可部署资产的多组件。 |
| 9. | Of course , you ll need to answer some basic questions about your vob structure , most of which you may already have answered in your cm plan 当然,你将会需要回答一些有关你的vob结构的基本问题,这些问题的大多数可能已经在你的配置管理计划里进行了回答: |
| 10. | If closed packages are going to be used on a regular basis then staging vobs may not be required since tivoli software distribution manages its own staging environment that allows you to perform diff s between several stored packages 如果封闭包将被用于常规操作,那么就不需要分段进阶vob了,因为tivoli软件发布会管理自己的分段进阶环境,这使得你能够处理多个保存的包之间的差异。 |