]> Launch a private p4d in a local directory If you are working with an offline repository in a local directory, vcp can launch a p4d in that directory on a random high numbered TCP port for you. p4 require VCP::Dest::p4; $ui->{Dest} = VCP::Dest::p4->new; $ui->{Dest}->repo_scheme( 'p4' ); yes $ui->{Dest}->{P4_RUN_P4D} = 1; no Directory to run p4d in Enter the directory to launch the p4d in. VCP will then check that this is a valid directory. $ui->{Dest}->repo_server( $answer ); $ui->{Dest}->repo_id( "p4:" . $answer ); P4 Host name, including port Enter the name and port of the p4d to read from, separated by a colon. Leave empty to use the p4's default of the P4HOST environment variable if set or "perforce:1666" if not. $ui->{Dest}->repo_server( $answer ); $ui->{Dest}->repo_id( "p4:" . $answer ); P4 user id Enter the user_id (P4USER) value needed to access the server. Leave empty to the P4USER environemnt variable, if present; or the login user if not. $ui->{Dest}->repo_user( $answer ); Password If a password (P4PASSWD) is needed to access the server, enter it here. WARNING: password will be echoed in plain text to the terminal. $ui->{Dest}->repo_password( $answer ); Files to copy The destination spec is a perforce repository spec and must begin with // and a depot name ("//depot"), not a local filesystem spec or a client spec. There should be a trailing "/..." specified. guard="qr#\A//[^.]*\.{3}\z#" //... $ui->{Dest}->repo_filespec( $answer ); Change branch rev #1 Forces VCP to do a p4 integrate, add, submit sequence to branch files, thus capturing the branch and the file alterations in one change. $ui->{Dest}->{P4_CHANGE_BRANCH_REV_1} = 1; $ui->{Dest}->init;