Helix SwarmHelix Swarm

p4.html

  • //
  • guest/
  • timothee_besset/
  • docs/
  • html/
  • VCP/
  • Source/
  • p4.html #1
  • View
  • Commits
  • Open Download .zip Download (6 KB) 
  1. <html><head><title>VCP::Source::p4 - A Perforce p4 repository source</title></head><body><h1><a name="NAME">NAME
  2.  
  3. </a></h1><p>VCP::Source::p4 - A Perforce p4 repository source
  4.  
  5. <p><hr><h1><a name="SYNOPSIS">SYNOPSIS
  6.  
  7. </a></h1><pre>   vcp p4://depot/...@10          # all files after change 10 applied
  8.    vcp p4://depot/...@1,10        # changes 1..10
  9.    vcp p4://depot/...@-2,10       # changes 8..10
  10.    vcp p4://depot/...@1,#head     # changes 1..#head
  11.    vcp p4://depot/...@-2,#head    # changes 8..10
  12.    vcp p4:...@-2,#head            # changes 8..10, if only one depot
  13.  
  14. </pre><p>To specify a user name of 'user', P4PASSWD 'pass', and port 'host:1666',
  15. use this syntax:
  16.  
  17. <pre>   vcp p4:user(client)password@host:1666:files
  18.  
  19. </pre><p>Note: the password will be passed in the environment variable P4PASSWD
  20. so it shouldn't show up in error messages. This means that a password
  21. specified in a P4CONFIG file will override the password you set on the
  22. command line. This is a bug.  User, client and the server string will be
  23. passed as command line options to make them show up in error output.
  24.  
  25. <p>You may use the P4... environment variables instead of any or all of the
  26. fields in the p4: repository specification.  The repository spec
  27. overrides the environment variables.
  28.  
  29. <p><hr><h1><a name="DESCRIPTION">DESCRIPTION
  30.  
  31. </a></h1><p>Driver to allow <a href="../../vcp.html">vcp</a> to extract files from a
  32. <a href="http://perforce.com/">Perforce</a> repository.
  33.  
  34. <p>Note that not all metadata is extracted: users, clients and job tracking
  35. information is not exported, and only label names are exported.
  36.  
  37. <p>Also, the 'time' and 'mod_time' attributes will lose precision, since
  38. p4 doesn't report them down to the minute.  Hmmm, seems like p4 never
  39. sets a true mod_time.  It gets set to either the submit time or the
  40. sync time.  From <code>p4 help client</code>:
  41.  
  42. <pre>    modtime         Causes 'p4 sync' to force modification time 
  43. 		    to when the file was submitted.
  44.  
  45. </pre><pre>    nomodtime *     Leaves modification time set to when the
  46. 		    file was fetched.
  47.  
  48. </pre><p><hr><h1><a name="OPTIONS">OPTIONS
  49.  
  50. </a></h1><dl><dt><a name="_b_bootstrap_"><strong><p>-b, --bootstrap
  51.  
  52. </strong></a><pre>   -b '...'
  53.    --bootstrap='...'
  54.    -b file1[,file2[,...]]
  55.    --bootstrap=file1[,file2[,...]]
  56.  
  57. </pre><dd>(the <code>...</code> there is three periods, a p4 wildcard implemented by
  58. <a>Regexp::Shellish</a>.
  59.  
  60. <p>Forces bootstrap mode for an entire export (-b '...') or for certain
  61. files.  Filenames may contain wildcards, see <a>Regexp::Shellish</a> for
  62. details on what wildcards are accepted.
  63.  
  64. <p>Controls how the first revision of a file is exported.  A bootstrap
  65. export contains the entire contents of the first revision in the revision
  66. range.  This should only be necessary when exporting for the first time.
  67.  
  68. <p>An incremental export contains a digest of the revision preceding the first
  69. revision in the revision range, followed by a delta record between that
  70. revision and the first revision in the range.  This allows the destination
  71. import function to make sure that the incremental export begins where the
  72. last export left off.
  73.  
  74. <p>The default is decided on a per-file basis: if the first revision in the
  75. range is revision #1, the full contents are exported.  Otherwise an
  76. incremental export is done for that file.
  77.  
  78. <p>This option is necessary when exporting only more recent revisions from
  79. a repository.
  80.  
  81. <dt><a name="_follow_branch_into_"><strong><p>--follow-branch-into
  82.  
  83. </strong></a><dd>Causes VCP to notice &quot;branch into&quot; messages in the filelog and, if the
  84. target revision number is #1, add the target file to the list of exported
  85. files.  This usually needs a --rev-root option to set the rev root to
  86. be high enough in the directory tree to include all branches (it's an
  87. error to export a file that is not under the rev root).
  88.  
  89. <dt><a name="_r_rev_root_"><strong><p>-r, --rev-root
  90.  
  91. </strong></a><dd>Sets the &quot;revisions&quot; root of the source tree being extracted; without this
  92. option, VCP assumes that you are extracting the directory tree ending in the
  93. last path segment in the filespec without a wildcard.  This allows you to
  94. specify a shorter root directory, which can be useful especially with
  95. --follow-branch-into, since branches may often lead off from the current
  96. directory to peer directories or even in to entirely different trees.
  97.  
  98. <p>The default <code>rev-root</code> is the file spec up to the first path segment
  99. (directory name) containing a wildcard, so
  100.  
  101. <pre>   p4:/a/b/c...
  102.  
  103. </pre><p>would have a rev root of <code>/a/b</code>.
  104.  
  105. <p>In direct repository-to-repository transfers, this option should not be
  106. necessary, the destination filespec overrides it.
  107.  
  108. </dl><p><hr><h1><a name="LIMITATIONS">LIMITATIONS
  109.  
  110. </a></h1><p>Treats each branched file as a separate branch with a unique branch_id,
  111. although files that are branched together should end up being submitted
  112. together in the destination repository due to change number aggregation.
  113.  
  114. <p>Ignores branch specs for now.  There may be an option to enable
  115. automatic use of branch specs because most are probably well behaved.
  116. However, in the event of a branch spec being altered after the original
  117. branch, this could lead to odd results.  Not sure how useful branch
  118. specs are vs. how likely a problem this is to be.  We may also want to
  119. support &quot;external&quot; branch specs to allow deleted branch specs to be
  120. used.
  121.  
  122. <p><hr><h1><a name="SEE_ALSO">SEE ALSO
  123.  
  124. </a></h1><p><a href="../Dest/p4.html">VCP::Dest::p4</a>, <a href="../../vcp.html">vcp</a>.
  125.  
  126. <p><hr><h1><a name="AUTHOR">AUTHOR
  127.  
  128. </a></h1><p>Barrie Slaymaker &lt;barries@slaysys.com&gt;
  129.  
  130. <p><hr><h1><a name="COPYRIGHT">COPYRIGHT
  131.  
  132. </a></h1><p>Copyright (c) 2000, 2001, 2002 Perforce Software, Inc.
  133. All rights reserved.
  134.  
  135. <p>See <a href="../License.html">VCP::License</a> (<code>vcp help license</code>) for the terms of use.
  136.  
  137. <p><hr><i><font size="-1">Last updated: Fri Nov  8 13:07:23 2002</font></i></body></html>
# Change User Description Committed
#1 4040 timothee_besset guest branch 21 years ago
//guest/perforce_software/revml/docs/html/VCP/Source/p4.html
#2 2307 Barrie Slaymaker get VCP::Filter::map working, update docs 22 years ago
#1 1993 Barrie Slaymaker Check in HTML documentation 23 years ago