CopyFromVersionMapDoc.tioga
Copyright © 1986 by Xerox Corporation. All rights reserved.
Russ Atkinson (RRA) June 9, 1986 12:06:13 pm PDT
Spreitzer, April 24, 1986 12:08:10 pm PST
COPY FROM VERSION MAP
CEDAR 6.1 — FOR INTERNAL XEROX USE ONLY
CopyFromVersionMap
-- to copy files using version maps
Russ Atkinson
© Copyright 1986 Xerox Corporation. All rights reserved.
Abstract: CopyFromVersionMap allows a user to setup a local subdirectory using a pair of version maps (one for source, one for symbols) such that all of the files listed in the version maps have local attachments in that subdirectory.
Created by: Russ Atkinson
Maintained by: Russ <Atkinson.pa>
Keywords: copy, version map
XEROX Xerox Corporation
Palo Alto Research Center
3333 Coyote Hill Road
Palo Alto, California 94304
For Internal Xerox Use Only
CopyFromVersionMap
CopyFromVersionMap allows a user to setup a local subdirectory using a pair of version maps (one for source, one for symbols) such that all of the files listed in the version maps have local attachments in that subdirectory.
There is both a Cedar interface (CopyFromVersionMap), and a command tool command (CopyFromVersionMap). The command tool command is documented below; the Cedar interface is similar.
The CopyFromVersionMap command takes one (optional) argument, which is the prefix to be used for the version maps. The file names of the version maps must match "*Source.VersionMap" and "*Symbols.VersionMap". If the prefix is not specified, then the switches can be used to specify one of the well-known version map prefixes:
-c: CedarChest ("[Cedar]<CedarChest6.1>VersionMap>CedarChest")
User can alter default via profile option CopyFromVersionMap.CedarChestPrefix.
-d: DATools ("[DATools]<DATools6.1>DAWorldAdministration>DAWorldMap")
User can alter default via profile option CopyFromVersionMap.DAToolsPrefix.
-r: Cedar release ("[Cedar]<Cedar6.1>VersionMap>Cedar")
User can alter default via profile option CopyFromVersionMap.CedarPrefix.
-u: User profile option CopyFromVersionMap.DefaultPrefix
The switches can also specify other options:
-v: verbose (file names needing attachment are listed)
-w: warnings only (no attachments made)
-z: zap files even if version map file is older
The normal behavior is to refuse to make an attachment if a local version of the file exists and is unattached. This is done because the user may be editing this filee, and it would be unkind to overwrite the local file.
It is also considered unkind to make a new attachment if the local name is already attached to a more recent file. This feature allows a user to have a more recent test version of a package. However, when create dates are the same the version map is considered to be more accurate. This is a compromise that may not please everyone.
The z switch is meant to override these heuristics when the version map is believed to hold the more important truth. This might happen if there was a more recent version of a package started but then abandoned. The user should not use the z switch without examining the printed warnings from usage without the z switch.
The switches will default to FALSE except for those specified in the user profile option CopyFromVersionMap.DefaultSwitches.
As an example usage, consider the commands:
cdr DATools
change working directory to ///DATools/
CopyFromVersionMap -d
copy (attach) files using the standard DATools version maps
The above commands will form attachments in the ///DATools/ directory to the entire set of DATools listed in the standard version maps. As of April 16, 1986 there were 1147 files in these version maps. If CopyFromVersionMap is run for the first time on a Dorado, the above commands take a little less than 3 minutes. If CopyFromVersionMap is run when no attachments are necessary, then the above commands take about 40 seconds (mostly disk limited).