index.html #1 

<HTML>

<HEAD>

<TITLE>
VCP/RevML Project - Perforce Public Depot
</TITLE>

</HEAD>

<BODY BGCOLOR="#FFFFFF">
<CENTER>
<P>
<A NAME="toc"></A>
<h2>
<sub><a href="../index.html">Perforce Public Depot</a></sub><br>
The <tt>VCP</tt>/RevML Project
</H2>
<P>

<TABLE BORDER=0><TR><TD>
<B>
<UL>
<LI><A HREF="#about">About This Project</A>
<LI><A HREF="#docs">Documentation</A>
<LI><A HREF="#dist">The VCP Distribution</A>
</UL>
</B>
</TABLE>
</CENTER>
<br>
<br>
<br>

<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66>

<A NAME="about"></A>
<H2>About This Project
</H2>

<TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</TABLE>
<!------------------------------------------------------------------>

<p>
<table cellpadding=5%>
<tr>
<td valign=top>
<b>Content</b>
</td>
<td valign=top>

Perl code and documentation for the <b><tt>vcp</tt></b> (Versioned Copy)
tool and <b>RevML</b> (Revision Markup Language).

<p><tt>vcp</tt> is a tool for copying revision controlled files between
various SCM repositories.  For example, using <tt>vcp</tt>, it is
possible to copy the contents of a entire Perforce depot (or part of
one) into a depot on a different Perforce server or to copy the contents
of a CVS repository into a Perforce server (or vice-versa).

<p>
<tt>vcp</tt> currently supports bidirectional exchanges between any two
of:
<ul>
<li>RevML
<li><tt>CVS</tt>
<li>Perforce
<li>VSS (beta)</tt>
</ul>

<p>RevML is an XML language that represents file revisions, such as
those managed by Perforce and other version control and configuration
management systems. RevML provides a generic way to represent revisions,
distinct from any particular version control or SCM tool's format. It
forms the basis for other tools that operate on file revisions.

</td>
</tr>


<tr>
<td valign=top>
<b>Curator</b>
</td>
<td valign=top>
The current curator for this project is Barrie Slaymaker.  Please send
email to <a href="mailto:barries@slaysys.com">barries@slaysys.com</a> if
you would like to submit contributions or have questions.
</td>
</tr>


<tr>
<td valign=top>
<b>Mailing<br>List</b>
</td>
<td valign=top>

The
<a href="http://maillist.perforce.com/mailman/listinfo/revml"><b>revml</b>
mailing list</a> is used by contributors and users of RevML and <tt>vcp</tt>
for a general discussion of the development and use of these tools.

</td>
</tr>
</table>

<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66>

<A NAME="docs"></A>
<H2>Documentation
</H2>

<TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</TABLE>
<!------------------------------------------------------------------>

<p> <tt>vcp</tt> documentation is <a
href="http://public.perforce.com:8080/@cdf=//public/revml/docs/html/index.html&@//public/revml/docs/html/index.html">browsable
as HTML</a> via <a
href="http://public.perforce.com/public/index.html">the Perforce
repository.</a>

<p> In addition, please refer to the following files from the
distribution for more information:

<ul>
<li><b><a href=README>README</a></b>
<li><b><a href=INSTALL>INSTALL</a></b>
<li><b><a href=CHANGES>CHANGES</a></b>
<li><b><a href=LICENSE>LICENSE</a></b> (BSD-style)
<li><b><a href=MANIFEST>MANIFEST</a></b>
</ul>

<p>All of the documentation is embedded in files in <a
href="http://public.perforce.com:8080/@md=d&cd=//public/revml/&ra=s&c=E7O@//public/revml/bin/?ac=83"><tt>bin/</tt></a>
and <a
href="http://public.perforce.com:8080/@md=d&cd=//public/revml/&ra=s&c=E7O@//public/revml/lib/?ac=83"><tt>lib/...</tt></a>
using POD (Plain Old Documentation).  The <tt>vcp help</tt> command
gives command-line access to all documentation, but lists user
documentation by default.  The <tt>vcp help <i>dest_dir</i></tt> command
can be used to build your own local copy of the documentation as HTML
(this is what is used to generate the HTML documentation linked to
above).

<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%><TR><TD BGCOLOR=FFCC66>

<A NAME="dist"></A>
<H2>The VCP Distribution
</H2>

<TD WIDTH=5% BGCOLOR=FFCC66 ALIGN=RIGHT><FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</TABLE>
<!------------------------------------------------------------------>

<p>VCP is primarily distributed as a single Perl file with most of 
the prerequisite modules built-in.  This is available from:
<a
href="http://public.perforce.com:8080/@md=d&cd=//public/revml/dist/&cdf=//public/revml/dist/vcp.pl@//public/revml/dist/vcp.pl">//public/revml/dist/vcp.pl</a>

<p>In order to modify VCP, you'll need a number of prerequisite modules
installed and VCP itself.  The most up to date (and possibly unreleased)
files comprising the current distribution of VCP (which includes the DTD
and support files for RevML) are available for direct browsing and
downloading from the Perforce Public Depot at

<blockquote><b> <A
HREF="http://public.perforce.com:8080/@ra=s@/public/revml/">
//public/revml/...</a> </b></blockquote>

<p>VCP may be downloaded from the Public Depot using any Perforce
client software

<p>The easiest way to install VCP for hacking is to run Unix and
use perl's CPAN.pm:

<blockquote><b><tt>perl -MCPAN -e "install VCP"</tt></b></blockquote>

<p>This will track down all dependencies and install them.  For working
with the source on Windows, you'll need to install the ppms for
XML::Parser and several other modules.  <a
href="mailto:barries@slaysys.com">Contact me</a> for help with this.


<!------------------------------------------------------------------>


<br><br><br>
<!------------------------------------------------------------------>
<P>
<TABLE CELLSPACING=0 BORDER=0 WIDTH=100%>
<TR>

<TD WIDTH=15% BGCOLOR=FFCC66 ALIGN=LEFT VALIGN=CENTER>
<FONT SIZE="-2">
Copyright &copy;<br>
1998, 1999<br>
<a href="http://www.perforce.com">Perforce Software</a><br>
</FONT>
</TD>

<TD WIDTH=70% BGCOLOR=FFCC66 ALIGN=CENTER>
<FONT SIZE="-2">
You're browsing a file stored as<br> 
<code>$Id: //guest/timothee_besset/index.html#1 $</code><br> 
in the 
<A HREF=http://public.perforce.com/public/index.html>Perforce Public Depot</A>.
</FONT>
</TD>

<TD WIDTH=15% BGCOLOR=FFCC66 ALIGN=RIGHT>
<FONT SIZE="-2"><A HREF="#toc">
Back to<BR>Table of<BR>Contents</A></TD></TR>
</FONT>
</TD>

</TR>
</TABLE>
<!------------------------------------------------------------------>



</BODY>
# Change User Description Committed
#1 4040 timothee_besset guest branch
//guest/perforce_software/revml/index.html
#7 1996 Barrie Slaymaker Refer to the vcp.pl "fat" distribution
#6 1995 Barrie Slaymaker Improve links to source directory
       Move documentation info above source code browsing info
       Show how to get command line help and how to
       generate local HTML documentation
#5 1994 Barrie Slaymaker Make VCP the primary subject of the page instead of RevML.
       Point to the HTML docs in the repository browser.
#4 1992 Barrie Slaymaker Add VSS notification.
#3 1155 rmg The change to utils/index.html was required to get the page
       to render better with Netscape 6.2. (Without the closing </B>
       tags, the whole page from the Depot Browsers section on down
       rendered bold...!)

       I made the same logical change to the other four for consistency,
       though they didn't seem to suffer from the same problem.

       p4dti/index.html still doesn't render right under Netscape 6.2,
       but it's from a different patterns and I couldn't see a quick
       clean fix... so I didn't mess with it for now.
#2 776 rmg Adjust the revml index (per feedback from barries and others)
and point the top level index link at it.
#1 775 rmg First cut index page for RevML.