<html><head><title>VCP::Dest::vss - vss destination driver</title></head><body><h1><a name="NAME">NAME
</a></h1><p>VCP::Dest::vss - vss destination driver
<p><hr><h1><a name="SYNOPSIS">SYNOPSIS
</a></h1><pre> vcp <source> vss:module
vcp <source> vss:SSDIR:module
vcp <source> vss:SSUSER@SSDIR:module
vcp <source> vss:SSUSER:PASSWORD@SSDIR:module
</pre><p>where module is a module or directory that already exists within VSS.
<p>SSDIR is the value to set the SSDIR environment variable to before
running SS.EXE and is a path to the sourcesafe directory.
<p>This destination driver will check out the indicated destination in
a temporary directory and use it to add, delete, and alter files.
<p><hr><h1><a name="DESCRIPTION">DESCRIPTION
</a></h1><p><b>Experimental</b>. See <a href="#NOTES">NOTES</a> for details.
<p>This driver allows <a href="vcp.html">vcp</a> to insert revisions in to a VSS
repository. There are no options at this time.
<p><hr><h1><a name="OPTIONS">OPTIONS
</a></h1><dl><dt><a name="_dont_recover_deleted_files_"><strong><p>--dont-recover-deleted-files
</strong></a><dd>VSS, at least as of V6, does not allow you to repeatedly delete and
recover a file. So VCP::Dest::vss normally forces VSS to recover
a deleted file when a new revision shows up, which is close as it
can get to CVS or p4 semantics.
<p>However, when coming from a VSS repository, it's ok to leave deleted files
lie. Use this option in that case.
<dt><a name="_mkss_ssdir_"><strong><p>--mkss-ssdir
</strong></a><dd>Make a new VSS database in directory named in the SSDIR portion of the
vss: specification. The directory must be nonexistant or empty.
The database is created using the MKSS, DDCONV, and DDUPD commands.
<p>NOTE: you need to use the SSUSER "Admin" to use this option (or tell
me how to add users from the command line).
<dt><a name="_delete_ssdir_"><strong><p>--delete-ssdir
</strong></a><dd>This option causes the --mkss option to delete the SSDIR if it exists
(including any contents). THIS IS DANGEROUS AND SHOULD ONLY BE USED
IN TEST ENVIRONMENTS.
</dl><p><hr><h1><a name="TODO">TODO
</a></h1><p>This module is here purely to support the VCP test suite, which must
import a bunch of files in to VSS before it can test the export. It works,
but is not field tested.
<p>While I'm sure there exist pressing reasons for importing files in to
VSS from other repositories, I have never had such a request and do not
wish to invest a lot of effort in advance of such a request.
<p>Therefore, this module does not batch checkins, cope with branches,
optimize comment settings, etc.
<p>Patches or contracts welcome.
<p><hr><h1><a name="NOTES">NOTES
</a></h1><p>VSS does not flag individual revisions as binary vs. text; the change is
made on a per-file basis. This module does not alter the filetype on
<code>Checkin</code>, however it does set binary (-B) vs. text (-B-) on <code>Add</code>.
<p>VSS allows one label per file, and adding a label (by default) causes a
new versions of the file. This module adds the first label it receives
for a file (which is first may or may not be predictable depending on
the source repository) to the existing version unless the existing
version already has a label, then it just adds new versions as needed.
<p>This leads to the backfilling issue: when backfilling, there are no labels
to request, so backfilling always assumes that the most recent rev is the
base rev for incremental imports.
<p>The <code>ss Delete</code> and <code>ss Share $file</code> commands do not allow a comment.
<p>Files are recalled from deleted status when added again if they were
deleted.
<p><hr><h1><a name="LIMITATIONS">LIMITATIONS
</a></h1><p>Built and tested against VSS v6.0 only.
<p><hr><h1><a name="AUTHOR">AUTHOR
</a></h1><p>Barrie Slaymaker <barries@slaysys.com>
<p><hr><h1><a name="COPYRIGHT">COPYRIGHT
</a></h1><p>Copyright (c) 2000, 2001, 2002 Perforce Software, Inc.
All rights reserved.
<p>See <a>VCP::License</a> (<code>vcp help license</code>) for the terms of use.
<p><hr><i><font size="-1">Last updated: Fri Jun 4 14:21:30 2004</font></i></body></html>