Product | Command Type |
---|---|
ClearCase | cleartool subcommand |
ClearCase LT | cleartool subcommand |
Attache | command |
Platform |
---|
UNIX |
Windows |
ClearCase and ClearCase LT-Update elements using the graphical update tool:
ClearCase and ClearCase LT-Update elements from the command line:
ClearCase and ClearCase LT-Load elements from the command line by specifying one or more load rules:
Attache:
For one or more loaded elements, the update command does the following:
Reevaluates the config spec to select a versions of loaded elements in the VOB, and loads them if they differ from the currently loaded element versions
Unloads the file or directory from the view if a loaded element is no longer visible (that is, a new directory version doesn't have an entry for the element). To unload a directory element, ClearCase and ClearCase LT
Recursively delete all loaded elements
Rename the directory to directory-name.unloaded if necessary, thus preserving all view-private files and view-private directories.
If the version in the snapshot view is different from the version in the VOB selected by the config spec, copies the version selected by the config spec into the view. The version in the view can be different if, for example, the selected version in the VOB is newer, or if a label is attached to the selected version in the VOB, but not to the version in the view
update does not apply to files or directories that are checked out to the current view.
If update cannot access a VOB (perhaps due to problems in the network), any elements from that VOB remain loaded, but are put in a special state (rule unavailable
).
The update command accounts for the fact that VOB elements specified by your config spec may change while an update is in progress. To avoid loading an inconsistent set of element versions, update ignores versions that meet both of the following criteria:
The version is selected by a config spec rule that specifies the LATEST version label.
The version was checked in after the moment the update operation began.
update also accounts for the fact that the system clocks on different hosts may not be synchronized.
When issued from a snapshot view,the following cleartool commands invoke update at the completion of the command:
findmerge (only when used to merge versions of a directory)
merge (only when used to merge versions of a directory)
The form of the update command that specifies the -add_loadrules option enables you to add new load rules to your config_spec and load the elements that those rules specify.
This command downloads the specified files to the workspace.
USING THE GRAPHICAL UPDATE TOOL. Default: The update is performed in the command window.
USING THE PREVIEW MODE. Default: None.
CONFIRMATION STEP. Default: update prompts for confirmation of the elements to be updated. However, update does not in all circumstances prompt you to confirm all the elements to be updated. Sometimes there are no confirmation prompts when you update elements, even though you have not specified -force.
HANDLING HIJACKED FILES. Default: Leaves all hijacked files in the view with their current modifications (-noverwrite).
SPECIFYING A FILE TRANSFER LOG. Default: A log file named update.timestamp.updt that is written to the root of the snapshot view directory.
SPECIFYING NEW LOAD RULES. Default: None.
SPECIFYING THE ELEMENTS TO BE UPDATED OR ADDED. Default: If you do not specify -add_loadrules, the current snapshot view; if you specify -add_loadrules, none.
SPECIFYING THE FILES TO BE UPDATED. Default: None.
DISPLAY FILES TO BE UPDATED. Default: None.
SPECIFYING HOW THE FILES ARE TO BE UPDATED. Default: When a directory is specified, its file contents are updated. If a destination file already exists that is identical in contents with the source file, it is not overwritten. If an existing destination file is read-only and differs from the source, it is always overwritten. If the destination file exists and is writable, an overwrite query is issued.
HANDLING OF DIRECTORY ARGUMENTS. Default: For each pname that specifies a directory element, update downloads to the Attache workspace the contents of that directory, but not the contents of any of its subdirectories.
SPECIFYING A FILE TRANSFER LOG. Default: None.
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.
NOTE: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf-for example, /vobs/src. A single-component VOB tag consists of a leaf only-for example, /src. In all other respects, the examples are valid for ClearCase LT.
Preview an update of the view darren_3.2 and produce a log file in the C:\temp directory.
cmd-context update -print -log C:\temp E:\views\darren_3.2
Update the file ./foo.c using the current time as the time stamp.
cmd-context update -ctime foo.c
Update the current directory; if there are any hijacked files, rename them filename.keep and copy the VOB versions specified by the config spec into the view.
cmd-context update -rename
Load into the current view the new elements in .\vobs\doc\user_manual, adding the rule load \vobs\doc\user_manual
to the view's config spec.
cmd-context update -add_loadrules \vobs\doc\user_manual
Determine which files have been changed since yesterday in the /vobs/proj VOB.
cmd-context update -print -since yesterday -r /vobs/proj
Update all files changed since yesterday in the \proj_vob VOB, overwriting any writable files in the workspace.
cmd-context update -since yesterday -r -overwrite \proj_vob
Download all files specified by the c:\users\jed\proj.ws project config file.
cmd-context update -all -r @c:\users\jed\proj.ws
Update any files changed since the last update using the c:\users\jed\proj.ws project config file, logging results to the c:\users\jed\proj.log file.
cmd-context update -r -log c:\users\jed\proj.log @c:\users\jed\proj.ws
checkin, checkout, clearviewupdate, config_spec, edcs, get, findmerge, ln, merge, mkdir, mkelem, mv, rmname, setcs, uncheckout
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |