view release on metacpan or  search on metacpan

SYNCTREE.html  view on Meta::CPAN

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>&lt;src&gt;</em> but not in <em>&lt;dest&gt;</em>, modify any files which
exist in both but differ, but <strong>not</strong> to remove files which are present
in <em>&lt;dest&gt;</em> and not in <em>&lt;src&gt;</em>.  Adding the
<em>-rmname</em> flag will cause this removal to happen as well and thus make
the <em>&lt;src&gt;</em> and <em>&lt;dest&gt;</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

synctree  view on Meta::CPAN

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.

=head1 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 I<clearfsimport>,
I<citree>, and I<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 config records (CR's) and labels, or similar.

The default operation is to mkelem all files which exist in
I<E<lt>srcE<gt>> but not in I<E<lt>destE<gt>>, modify any files which
exist in both but differ, but B<not> to remove files which are present
in I<E<lt>destE<gt>> and not in I<E<lt>srcE<gt>>.  Adding the
I<-rmname> flag will cause this removal to happen as well and thus make
the I<E<lt>srcE<gt>> and I<E<lt>destE<gt>> areas identical.