VCP::Source::p4 - A Perforce p4 repository source
vcp p4://depot/...@10 # all files after change 10 applied vcp p4://depot/...@1,10 # changes 1..10 vcp p4://depot/...@-2,10 # changes 8..10 vcp p4://depot/...@1,#head # changes 1..#head vcp p4://depot/...@-2,#head # changes 8..10 vcp p4:...@-2,#head # changes 8..10, if only one depot
To specify a user name of 'user', P4PASSWD 'pass', and port 'host:1666', use this syntax:
Note: the password will be passed in the environment variable P4PASSWD so it shouldn't show up in error messages. This means that a password specified in a P4CONFIG file will override the password you set on the command line. This is a bug. User, client and the server string will be passed as command line options to make them show up in error output.
You may use the P4... environment variables instead of any or all of the fields in the p4: repository specification. The repository spec overrides the environment variables.
Note that not all metadata is extracted: users, clients and job tracking information is not exported, and only label names are exported.
Also, the 'time' and 'mod_time' attributes will lose precision, since p4 doesn't report them down to the minute. Hmmm, seems like p4 never sets a true mod_time. It gets set to either the submit time or the sync time. From
p4 help client:
modtime Causes 'p4 sync' to force modification time to when the file was submitted. nomodtime * Leaves modification time set to when the file was fetched.
- -b, --bootstrap
-b '...' --bootstrap='...' -b file1[,file2[,...]] --bootstrap=file1[,file2[,...]]
...there is three periods, a Regexp::Shellish wildcard borrowed from
Forces bootstrap mode for an entire export (-b '...') or for certain files. Filenames may contain wildcards, see Regexp::Shellish for details on what wildcards are accepted.
Controls how the first revision of a file is exported. A bootstrap export contains the entire contents of the first revision in the revision range. This should only be necessary when exporting for the first time.
An incremental export contains a digest of the revision preceding the first revision in the revision range, followed by a delta record between that revision and the first revision in the range. This allows the destination import function to make sure that the incremental export begins where the last export left off.
The default is decided on a per-file basis: if the first revision in the range is revision #1, the full contents are exported. Otherwise an incremental export is done for that file.
This option is necessary when exporting only more recent revisions from a repository.
- -r, --rev-root
Falsifies the root of the source tree being extracted; files will appear to have been extracted from some place else in the hierarchy. This can be useful when exporting RevML, the RevML file can be made to insert the files in to a different place in the eventual destination repository than they existed in the source repository.
rev-rootis the file spec up to the first path segment (directory name) containing a wildcard, so
would have a rev-root of
In direct repository-to-repository transfers, this option should not be necessary, the destination filespec overrides it.
Creates a new instance of a VCP::Source::p4. Contacts the p4d using the p4 command and gets some initial information ('p4 info' and 'p4 labels').
Barrie Slaymaker <email@example.com>
Copyright (c) 2000, 2001, 2002 Perforce Software, Inc. All rights reserved.
See VCP::License (
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 601:
You forgot a '=back' before '=head1'