VCP::Dest::vss - vss destination driver
vcp <source> vss:module vcp <source> vss:VSSROOT:module
where module is a module or directory that already exists within VSS.
This destination driver will check out the indicated destination in a temporary directory and use it to add, delete, and alter files.
Experimental. See NOTES for details.
This driver allows vcp to insert revisions in to a VSS repository. There are no options at this time.
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.
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.
Therefore, this module does not batch checkins, cope with branches, optimize comment settings, etc.
Patches or contracts welcome.
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
Checkin, however it does set binary (-B) vs. text (-B-) on Add.
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.
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.
The ss Delete command does not allow a comment.
Files are recalled from deleted status when added again if they were deleted.
Barrie Slaymaker <barries@slaysys.com>
Copyright (c) 2000, 2001, 2002 Perforce Software, Inc. All rights reserved.
See VCP::License (vcp help license) for the terms of use.