THIS IS ONLY FOR USE WITH PERFORCE SERVERS BEFORE 15.1 In Perforce 2015.1, features to support Distributed Versioning have been added! Please see the 'myb4' project for an experimental usability/convention script to be used around the 2015.1 version of Perforce. === Basic Install: -------------- 1) Install this 'p4' into your HOME/bin directory (assuming that is in your PATH) 2) Edit this 'p4' to specify your platform if different from darwin90x86_64, see ftp.perforce.com/perforce/r14.1 for possible platforms 3) Make 'p4' executable: chmod a+x $HOME/p4 4) Check to make sure this is the 'p4' that you're using: which p4 Alternative Install: -------------------- Put this 'p4' in some directory FOO alias p4="FOO/p4 " Then you can run 'p4' and use this script or run '\p4' and use the raw p4 Interesting tidbits: -------------------- - This will reuse your P4CONFIG/P4IGNORE if defined - Sets the user to use for remote depot access This means you can create a remote depot mapped to something and pull content into your local Perforce storage structure. (You need to log into the remote server for authentication to work) Available commands: ------------------- p4 init {directory} Create a Perforce storage structure in the current or specified sub-directory p4 check Check for a new version of this script When in a Perforce storage structure: p4 switch {branchName} Switch to specified branch or report current Check for pending work and do something p4 switch -b newBranchName Create new branch or report current Check for pending work and do something Switches to new branch p4 switch -a List the defined branches p4 branch FROM-TO Define how to merge between two branches Only needed if branches use multi-line views p4 mergefrom BRANCHNAME Run integ from named branch into current one Uses branchspec BRANCH1-BRANCH2 if it exists Otherwise //branches/FROM/... //branches/CUR/... Then runs 'p4 resolve -am' Note: This is not a supported Perforce product or tool. You're on your own when using this wrapper. Note: There are no guardrails! Use identifiers for branch names for best results.