The clearexport_sccs command exports Source Code Control System (SCCS) files so that they can be imported into ClearCase or ClearCase LT elements and versions. The source data can range from a single file to an entire directory tree.
During the export stage, you invoke clearexport_sccs in the area where the SCCS files reside. clearexport_sccs creates a datafile (by default, named cvt_data) that contains descriptions of elements, branches, and versions. If any of the files to be processed reside below (rather than in) the current working directory, clearexport_sccs includes descriptions of the corresponding directory elements in the datafile. clearexport_sccs follows symbolic links it encounters during the export stage.
In the import stage, you invoke clearimport on the datafile to import information into the new VOB.
clearexport_sccs ignores information in SCCS files that is not related to version-tree structure; this includes flags, ID keywords, user lists, and Modification Request numbers. You can specify a translation file to control naming, enforcing consistency over multiple invocations of clearexport_sccs. You can use the –V option to preserve SCCS IDs as attributes of the corresponding ClearCase or ClearCase LT versions.
clearexport_sccs and clearimport use magic files to determine which element type to use for each element that clearimport creates. For more information about magic files and file typing, see the cc.magic reference page.
Note: You cannot run clearexport_sccs on UNIX and then run clearimport on Windows to import the data, or vice versa. However, you can transfer data in either direction between UNIX and Windows by mounting the UNIX VOB or file system on your Windows machine and running both clearexport_sccs and clearimport on the Windows machine.
clearexport_sccs works directly with the structured SCCS s-files, which have the s. file name prefix. It does not process the g-files created with get and get –e commands. Be sure to check in such files with the delta command before running clearexport_sccs. clearexport_sccs issues warning messages when it encounters checked-out files, but it still processes them.
Other than issuing warning messages for checked-out files, clearexport_sccs ignores the p-files created by get –e.
If s-files are stored in SCCS (or sccs; case is not important) subdirectories, clearexport_sccs collapses the subdirectory level. For example, SCCS file ./proj/SCCS/s.main.c becomes element ./proj/main.c.
You can process an SCCS file in several passes. For example, you can use clearexport_sccs to process major revision level 1, and use it again to process major revision level 2. On the subsequent passes, clearimport updates an existing element correctly if that VOB element has not been modified in the interim.
During import, clearimport invokes a shell to extract data from the datafile. clearimport can handle some, but not all, characters that are special to shells. Import fails for any file name that includes any of these characters:
For example:
Before running clearexport_sccs, rename any file whose name contains these characters.
Note: If any datafile-pname or source-name that you specify include spaces, the file name requires special treatment. On UNIX, you must escape the space characters:
On Windows, you must enclose the name in double quotes:
An SCCS branch ID is a name for a particular branch of an SCCS file. clearexport_sccs translates the symbols to names of branch types. Suppose an SCCS symbol, rls_1.3_fixes, names a branch 3.5.1. clearexport_sccs exports a description of branch type rls_1.3_fixes, and clearimport creates a branch of that type at the ClearCase or ClearCase LT version created from SCCS revision 3.5.
You can enforce consistency of translation by using a translation file to control the names of branches created from SCCS branches. If you name such a file using the –T option, clearexport_sccs uses it as follows:
The first time you use clearexport_sccs, use –T to create a new translation file. On subsequent invocations of clearexport_sccs, use –T again, specifying the same translation file for consistent name translation.
The translation file consists of one or more lines in the following form:
For example, to rename the branch type pre_import_work to post_import_work and the branch type old_tests to obsolete_tests, the translation file contains the lines:
No blank lines are allowed in the file.
When clearexport_sccs encounters a file or directory that cannot be exported (for example, a file with format problems or a broken symbolic link), it prints an error and continues. After creating the data file, the command prints a summary of the files and directories that could not be exported.
clearexport_sccs determines whether to process an SCCS archive by using the last-modified date/time of the archive. If this date/time is before the date-time you specify with –s, clearexport_sccs does not process any of the revisions in the archive. If the archive's date/time is after the date-time you specify, clearexport_sccs processes the following revisions:
Note: In an incremental updating situation, if you remove a branch from an SCCS revision, clearimport does not remove the branch from the ClearCase or ClearCase LT element.
Specify the time as follows:
date.time | date | time |now where:
Specify time in 24-hour format, relative to the local time zone. If you omit the time, the default value is 00:00:00. If you omit date, the default is today. If you omit the century, year, or a specific date, the most recent one is used. Specify UTC if you want to resolve the time to the same moment in time regardless of time zone. Use the plus (+) or minus (-) operator to specify a positive or negative offset to the UTC time. If you specify UTC without hour or minute offsets, Greenwich Mean Time (GMT) is used. (Dates before January 1, 1970 Universal Coordinated Time (UTC) are invalid.)
If you use the –s option with this option, clearimport attaches SCCS_ID attributes only to revisions created after the date-time you specified.
Each attribute requires about 1 KB of storage in the VOB database.
On Windows systems, the value of the TMP environment variable.
Each source-name can be a simple file or directory name or a wildcard as described in wildcards_ccase. Specifying a parent directory (..) causes an error, as does any UNIX pathname that includes a slash or any Windows pathname that includes a slash or backslash. Run this command in a directory under which the elements to be exported reside. If the s-files reside in SCCS subdirectories, use the –r option to enable clearexport_sccs to find them.
cc.magic, clearexport_*, clearimport, delta, events_ccase, get, relocate, rcs(1), rsh(1) or remsh(1), sccs(1), wildcards_ccase
Copyright© 2003 Rational Software. All Rights Reserved.