ClearCase-SyncTree
view release on metacpan or search on metacpan
SYNCTREE.html view on Meta::CPAN
</head>
<body style="background-color: white">
<!-- INDEX BEGIN -->
<div name="index">
<p><a name="__index__"></a></p>
<ul>
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<li><a href="#options">OPTIONS</a></li>
<li><a href="#file_mapping">FILE MAPPING</a></li>
<li><a href="#comparisons">COMPARISONS</a></li>
<li><a href="#bugs">BUGS</a></li>
<li><a href="#debugging">DEBUGGING</a></li>
<li><a href="#author">AUTHOR</a></li>
<li><a href="#copyright">COPYRIGHT</a></li>
<li><a href="#see_also">SEE ALSO</a></li>
</ul>
<hr name="index" />
</div>
<!-- INDEX END -->
<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>synctree - Normalize a tree of flat files with a tree of ClearCase elements</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
<pre>
synctree -sbase /tmp/newcode -dbase /vobs_tps/xxx</pre>
<p>Take all files located under /tmp/newcode, remove the leading
"/tmp/newcode" from each of their pathnames, and place the remaining
relative paths under "/vobs_tps/xxx" as versioned elements, leaving
them checked out.</p>
<pre>
synctree -cr -yes -ci -sbase /vobs/hpux/bin -dbase /vobs_rel/hpux/bin</pre>
<p>Sync all files under "/vobs_rel/hpux/bin" with those in
"/vobs/hpux/bin", making sure to preserve their CR's. Suppress
interactive prompting and check in all work when done.</p>
<pre>
synctree -sb /A/B -db /X/Y -map /A/B/foo /X/Y/bar /A/B/here /X/Y/there</pre>
<p>Take 'foo' from directory /A/B and check it in as 'bar' in /X/Y.
Similarly, create an element /X/Y/there with the contents of /A/B/here.</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>Synctree brings a VOB area into alignment with a specified set of files
from a source area. It's analogous in various ways to <em>clearfsimport</em>,
<em>citree</em>, and <em>clearexport/clearimport</em>; 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 config records (CR's) and labels, or similar.</p>
<p>The default operation is to mkelem all files which exist in
<em><src></em> but not in <em><dest></em>, modify any files which
exist in both but differ, but <strong>not</strong> to remove files which are present
in <em><dest></em> and not in <em><src></em>. Adding the
<em>-rmname</em> flag will cause this removal to happen as well and thus make
the <em><src></em> and <em><dest></em> areas identical.</p>
<p>Synctree need not run in a view context itself but the directory named
by the <em>-dbase</em> flag must provide a view context. The branching
behavior of any checkouts performed will be governed by that view's
config spec. The <em>-dbase</em> 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.</p>
<p>The list of source files to operate on may be provided with the
<em>-flist</em> option or it may come from <code>@ARGV</code>. Any directories
encountered on the command line will be traversed recursively. If no
source-file-list is provided, the directory specified with <em>-sbase</em> is
used as the default.</p>
<p>File paths may be given as relative or absolute. Destination paths are
determined as follows: all source filenames are first turned into
absolute paths if necessary, then the source preface given with the
<em>-sbase</em> parameter is removed and replaced with the value of <em>-dbase</em>
to produce the destination pathname (but see FILE MAPPING below).</p>
<p>ClearCase symbolic links are supported, even on Windows. Note that,
unless you use the <em>-rellinks</em> flag, the text of the link is
transported <strong>verbatim</strong> from source area to dest area; thus relative
symlinks may no longer resolve in the destination area.</p>
<p>Consider using the <em>-n</em> flag the first time you use this on a valued
VOB, even though nothing irreversible (<em>rmelem</em>, <em>rmbranch</em>,
<em>rmver</em>, <em>rmtype</em>, etc.) is <strong>ever</strong> done by synctree. And by the
same token use <em>-yes</em> and <em>-ci</em> with care.</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
<p>Not all options are described here, only those requiring elaboration
beyond the <code>-help</code> summary. Run <code>synctree -help</code> for a full option
summary.</p>
<ul>
<li><strong><a name="force_stop" class="item"><em>-force, -stop</em></a></strong>
<p>By default, upon encountering a ClearCase error synctree will attempt
to return to the initial state by undoing all checkouts etc. The
<em>-stop</em> flag will cause it to exit immediately leaving the partial
state intact while <em>-force</em> will cause it to blunder onward, ignoring
errors. However, even with <em>-force</em> a nonzero status is returned if
errors are encountered.</p>
</li>
<li><strong><a name="ignore_co_overwrite_co" class="item"><em>-ignore_co, -overwrite_co</em></a></strong>
<p>By default, synctree refuses to run if any view-private files exist
under the destination base. This includes checkouts, which are a
special form of view private file. The <em>-ignore_co</em> flag allows
synctree to continue in this situation. As the flag name implies it
will <strong>ignore</strong> these checkouts; i.e. differences in the source base
will <em>not</em> overwrite the checked-out file in the destination. The
<em>-overwrite_co</em> flag also allows synctree to proceed in the presence
of existing checkouts but causes them to be overwritten by the source
version.</p>
( run in 2.324 seconds using v1.01-cache-2.11-cpan-5837b0d9d2c )