|
Size: 225
Comment:
|
← Revision 3 as of 2009-07-15 14:32:36 ⇥
Size: 489
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Diego, please describe the * export from Database into local CVS dir * comparison between versions * export /import from to CVS * tagging incl. tagging conventions start with : * Log in as"cususer" on PACS1 |
Configuration control of the CUS scripts in the database is performed automatically every time a script is amended or created. After you have Commited your work into the CUS registry (or inserted a file in the registry via ''cus -f -import''), you must invoke a dedicated ccm procedure: '''ccm -updatecus'''. This procedure will extract to temporary storage all modules in the CUS registry, perform a '''cvs commit''' and create a new CUS model in order to save the previous CUS version. |
Configuration control of the CUS scripts in the database is performed automatically every time a script is amended or created. After you have Commited your work into the CUS registry (or inserted a file in the registry via cus -f -import), you must invoke a dedicated ccm procedure: ccm -updatecus. This procedure will extract to temporary storage all modules in the CUS registry, perform a cvs commit and create a new CUS model in order to save the previous CUS version.