VCP-Source-p4.stml #6

<!DOCTYPE author [
  <!ENTITY yes_re "qr/\Ay(es)?\z/i" >
  <!ENTITY no_re "qr/\Ano?\z/i" >
  <!ENTITY yes_no_re "qr/\A(y(es)?|no?)\z/i" >
]>

<machine id="vcp">

  <!-- ================ TRANSITIONS =================== -->

  <state id="source_p4_run_p4d_prompt" class-ids="prompt_class">
    <name>Launch a private p4d in a local directory?</name>
    <description>
    
If you are working with an offline repository in a local directory, vcp
can launch a p4d in that directory on a random hi-numbered TCP port for
you.

    </description>

    <arc from="source_prompt">
      <description>p4</description>
    </arc>

    <arc to="source_p4_p4d_dir_prompt" guard="&yes_re;">
      <description>yes</description>
    </arc>

    <arc to="source_p4_host_prompt" guard="&no_re;">
      <description>No</description>
    </arc>

  </state>


  <state id="source_p4_p4d_dir_prompt" class-ids="prompt_class">
    <name>Directory to run p4d in?</name>
    <description>

Enter the directory to launch the p4d in.  VCP will test to see
if this is a valid directory when you hit Enter.
    
    </description>

    <arc to="dest_prompt"
        guard="sub { -d $_ ? 1 : die qw{'$_' is not a valid directory} }"
    />

  </state>

  <state id="source_p4_host_prompt" class-ids="prompt_class">
    <arc to="dest_prompt" />
  </state>


  <state id="rev_root" class-ids="prompt_state_class">
    <name>Enter rev-root</name>
    <description>
      sets the revisions root of the source tree being extracted.
    </description>
    <arc to="run_p4d" guard="validate rev-root"/>
  </state>


  <state id="run_p4d" class-ids="prompt_state_class">
    <name>Run p4d flag</name>
    <description>
      run a p4d instance in the directory indicated by repo_server.
    </description>
    <arc to="bootstrap" guard="&yes_no_re;"/>
  </state>


  <state id="bootstrap" class-ids="prompt_state_class">
    <name>Bootstrap mode export (Enter file wildcard)</name>
    <description>
      Forces bootstrap mode for an entire export (-b ...) or for certain
      files. Filenames may contain wildcards, see the Regexp::Shellish
      manpage for details on what wildcards are accepted.
    </description>
    <arc to="continue" guard="validate Regexp::Shellish wildcard"/>
  </state>


  <state id="continue" class-ids="prompt_state_class">
    <name>Continue Flag</name>
    <description>
      Starts this transfer where the previous one (to the same
      destination) left off. This uses the destination's state database to
      detect what was transferred last time and to begin this transfer
      where the previous one left off.
    </description>
    <arc to="follow_branch_into" guard="&yes_no_re;"/>
  </state>


  <state id="follow_branch_into" class-ids="prompt_state_class">
    <name>Follow 'branch into' flag</name>
    <description>
      Causes VCP to notice "branch into" messages in the output of p4's
      filelog command and. If the file that's the target of the p4
      integrate (branch) command is revision number #1, adds the target to
      the list of exported files. This usually needs a --rev-root option
      to set the rev root to be high enough in the directory tree to
      include all branches (it's an error to export a file that is not
      under the rev root).
    </description>
    <arc to="exit" guard="&yes_no_re;"/>
  </state>

</machine>