The London Perl and Raku Workshop takes place on 26th Oct 2024. If your company depends on Perl, please consider sponsoring and/or attending.
 / 
ClearCase-SyncTree-0.30
River stage zero No dependents
/ synctree

NAME

synctree - Normalize a tree of files with a tree of ClearCase elements

SYNOPSIS

  synctree -sbase /tmp/newcode -dbase /vobs_tps/xxx

Take all files located under /tmp/newcode/xxx, remove the leading "/tmp/newcode", from each of their pathnames, and place the remaining relative paths under "/vobs_tps/xxx".

  synctree -cr -yes -ci -sbase /vobs/hpux/bin -dbase /vobs_rel/hpux/bin

Sync all files under "/vobs_rel/hpux/bin" with those in "/vobs/hpux/bin", making sure to preserve their CR's. Suppress all interactive prompting.

  synctree -sb /A/B -db /X/Y -map /A/B/foo /X/Y/bar /A/B/here /X/Y/there

Take 'foo' from directory /A/B and check it in as 'bar' in /X/Y. Similarly for 'here' and 'there'.

DESCRIPTION

Synctree brings a VOB area into alignment with a specified set of files from a source area. It's analogous in various ways to clearfsimport, citree, and clearexport/clearimport; see the COMPARISONS section below. Synctree is useful if you have a ClearCase tree that must be kept in sync with a CVS tree during a transition period, or for overlaying releases of third-party products upon previous ones, or exporting deliverable DO's from a nightly build to a release VOB while preserving CR's and labels, or similar.

The default operation is to mkelem all files which exist in <src> but not in <dest>, modify any files which exist in both but differ, but not to remove files which are present in <dest> and not in <src>. The -rmname flag will cause this removal to happen as well.

Synctree need not run in a view context but the directory named by the -dbase flag must provide a view context. The branching behavior of any checkouts performed will be governed by that view's config spec. The -dbase directory need not exist, as long as it lies under a mounted VOB tag and in a view context. In other words, synctree can auto-create the destination directory tree.

The list of source files to operate on may be provided with the -flist option or it may come from @ARGV. Any directories encountered on @ARGV will be traversed recursively. If no source-file-list is provided, the directory specified with -sbase is used as the default.

File paths may be given as relative or absolute. Destination paths are determined as follows: all source filenames are first turned into absolute paths as necessary, then the path given with the -sbase parameter is removed and replaced with that of -dbase to produce the destination pathname (but see FILE MAPPING below).

ClearCase symbolic links are supported, even on Windows. Note that the text of the link is transported verbatim from source area to dest area; thus relative symlinks may no longer resolve in the destination area.

Consider using the -n flag the first time you use this on a valued VOB, even though nothing irreversible is done (e.g. no rmelem, rmbranch, rmver, rmtype, etc.). And by the same token use -yes and -ci with care.

OPTIONS

Not all options are described here, only those requiring elaboration beyond the -help summary. Run synctree -help for a full option summary.

  • -force, -stop

    By default, upon encountering a ClearCase error synctree will attempt to return to the initial state by undoing all checkouts etc. The -stop flag will cause it to exit immediately leaving the current state intact while -force will cause it to blunder onward, ignoring errors. However, even with -force a nonzero status is returned if errors are encountered.

  • -no, -yes, -ci

    The -no flag causes synctree to report what it would do and exit without making any changes, -yes suppresses all prompts except for the check in changes? prompt, and -ci suppresses that one. The default behavior is to prompt before making changes. To suppress all prompting you must use both -yes and -ci.

  • -label, -lbmods

    The -label option let you specify a label to be applied before finishing. By default it will label recursively from the -dbase area down, as well as all parent directories upward to the vob root. However, if the -lbmods flag is used in conjunction only modified elements will be labeled.

  • -reuse

    If element X is created in synctree run #1, rmname'd in run #2, and created again in run #3, you may end up with multiple elements with the same name. This situation is known as an evil twin. The -reuse flag can avoid this; before making a new element it searches the directory's version tree looking for a prior element of the same name. If found, it will link the old element back into the current version of the directory, then (if the contents differ) check it out and replace the contents with those of the source file.

    This flag can avoid evil twins and save storage space but will run a little slower due to the extra analysis. Also, there's no guarantee the prior element of the same name is in fact logically related to the new one. They could conceivably even be of different element types.

  • -Narrow

    The -Narrow flag allows a regular expression to limit the files from the source list which are compared with the destination base. I.e. if you want to transport all the *.class files from a dir tree without the source files you can use

        synctree -N '\.class\$' ...

    Note that the argument is a Perl regular expression, not a file glob. Any legal Perl RE may be used. Also, multiple -Narrow flags may be used; thus, to collect *.class and *.properties files you may use either of:

        synctree -N '\.class\$' -N '\.properties\$' ...
    synctree -N '\.(class|properties)\$' ...

    Also, the -Narrow flag is considered only for file lists derived internally by synctree. If you provide your own file list using -flist, filtering it is your own responsibility.

FILE MAPPING

Synctree has lots of support for remapping filenames. The options can be pretty confusing and thus deserve special treatment here.

Filename mapping is enabled with the -map flag. Without -map, a list of files provided on the command line is interpreted as a set of from files; their to paths are derived via s/^sbase/dbase/ and thus the file basenames do not change. In the presence of -map the @ARGV is instead interpreted as a hash alternating from and to names. Thus

  synctree -sb /etc -db /vobs_st/etc /etc/passwd /etc/group

would make two files under /vobs_st/etc called passwd and group, whereas

  synctree -sb /etc -db /vobs_st/etc -map /etc/passwd /vobs_st/etc/foo

would create one file (/vobs_st/etc/foo) which is a copy of /etc/passwd. Alternatively the mapping may be specified with a literal =>:

  synctree -sb /etc -db /vobs_st/etc -map '/etc/passwd => /vobs_st/etc/foo' ...

but note that this must be quoted against shell expansion. The => style is also allowed in files specified via -flist, thus:

  synctree -sb /etc -db /vobs_st/etc -flist - << EOF
  /etc/passwd => /vobs_st/etc/foo
  /etc/group  => /vobs_st/etc/bar
  EOF

COMPARISONS

Synctree is comparable to citree and clearfsimport. It is similar to citree but has more options and runs on both Windows and UNIX. It has the following advantages over clearfsimport:

  • Synctree works with all ClearCase versions whereas clearfsimport is first supported in CC 4.2.

  • Synctree is capable of preserving CR's during MVFS-MVFS> transfers whereas clearfsimport always treats the source area as flat files.

  • Synctree has support for mapping filenames in transit and a -Narrow option for limiting the set of files to transfer.

  • Synctree is built on a documented API (ClearCase::SyncTree) which may aid custom tool development in Perl whereas clearfsimport is a command-line interface only.

  • Synctree has support for element retention. I.e. if an element is added in one pass and removed (rmnamed) in a subsequent pass, and if a third pass would make another element of the same name, synctree can optionally (-reuse) make a link to the existing file instead of creating a new element which might be considered an "evil twin".

However, unless you need one of the above features the supported, integrated solution (clearfsimport) is generally preferable. And of course some of these features may eventually be supported by clearfsimport; check current documentation.

BUGS

  • Subtraction of symlinks is currently unimplemented (it's just a corner case I haven't gotten to).

  • SyncTree does not transport empty directories, and added/removed directories aren't shown explicitly in the list of operations to be performed. This is a structural artifact.

  • I have not tested SyncTree in snapshot views and would not expect it to work there without modifications.

DEBUGGING

The special flag -/dbg=1 will cause all underlying cleartool commands to be printed as they are run (this is actually a feature of the Argv module on which synctree is built).

AUTHOR

David Boyce <dsbperl@cleartool.com>

COPYRIGHT

Copyright (c) 2000,2001 David Boyce. All rights reserved. This Perl program is free software; you may redistribute and/or modify it under the same terms as Perl itself.

STATUS

This is currently ALPHA code and thus I reserve the right to change the UI incompatibly. At some point I'll bump the version suitably and remove this warning, which will constitute an (almost) ironclad promise to leave the interface alone.

PORTING

The guts of this program are in the ClearCase::SyncTree module, which is known to work on Solaris 2.6-7 and Windows NT 4.0SP3-5, and with perl 5.004_04 and 5.6. I would expect it to work on other Unix platforms too but have no way to find out.

SEE ALSO

perl(1), "perldoc ClearCase::SyncTree"

1 POD Error

The following errors were encountered while parsing the POD:

Around line 94:

=pod directives shouldn't be over one line long! Ignoring all 6 lines of content